Home
last modified time | relevance | path

Searched refs:rc1 (Results 1 – 25 of 36) sorted by relevance

12

/Linux-v5.4/Documentation/scsi/
DChangeLog.megaraid_sas7 Current Version : 06.803.02.00-rc1
8 Old Version : 06.803.01.00-rc1
20 Current Version : 06.803.01.00-rc1
21 Old Version : 06.700.06.00-rc1
33 Current Version : 06.700.06.00-rc1
34 Old Version : 06.600.18.00-rc1
43 Current Version : 06.600.18.00-rc1
44 Old Version : 06.506.00.00-rc1
63 Current Version : 06.506.00.00-rc1
64 Old Version : 06.504.01.00-rc1
[all …]
Dlpfc.txt19 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
72 At this time, the driver requires the 2.6.12 (if pre-release, 2.6.12-rc1)
/Linux-v5.4/drivers/staging/iio/Documentation/light/
Dsysfs-bus-iio-light-tsl2x7x2 KernelVersion: 3.3-rc1
9 KernelVersion: 3.3-rc1
/Linux-v5.4/Documentation/maintainer/
Dpull-requests.rst36 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
37 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
40 git tag -s char-misc-4.15-rc1 char-misc-next
42 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
95 Char/Misc patches for 4.15-rc1
97 Here is the big char/misc patch set for the 4.15-rc1 merge window.
129 git push origin char-misc-4.15-rc1
141 …-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-misc-4.15-rc1
146 'char-misc-4.15-rc1' tag location, to the head of the 'master'
153 If the char-misc-4.15-rc1 tag is not present in the repo that I am
[all …]
/Linux-v5.4/drivers/ide/
Dqd65xx.c427 int rc1, rc2 = -ENODEV; in qd65xx_init() local
432 rc1 = qd_probe(0x30); in qd65xx_init()
433 if (rc1) in qd65xx_init()
436 if (rc1 < 0 && rc2 < 0) in qd65xx_init()
/Linux-v5.4/arch/arm64/crypto/
Dsha512-ce-core.S83 .macro dround, i0, i1, i2, i3, i4, rc0, rc1, in0, in1, in2, in3, in4
84 .ifnb \rc1
85 ld1 {v\rc1\().2d}, [x4], #16
/Linux-v5.4/Documentation/translations/zh_CN/process/
D2.Process.rst45 将被称为4.14-rc1。RC1版本是一个信号，表示合并新特性的时间已经过去，稳定下一
62 二月 11 4.16-rc1, 合并窗口关闭
Dhowto.rst217 - 两个星期以后-rc1版本内核发布。之后只有不包含可能影响整个内核稳定性的
219 可能在-rc1后被接受是因为这样的修改完全独立，不会影响其他的代码，所以
220 没有造成内核退步的风险。在-rc1以后也可以用git向Linus提交补丁，不过所
/Linux-v5.4/drivers/net/wireless/ath/wil6210/
Dfw_inc.c660 int rc, rc1; in wil_request_firmware() local
677 for (sz = fw->size, d = fw->data; sz; sz -= rc1, d += rc1) { in wil_request_firmware()
678 rc1 = wil_fw_verify(wil, d, sz); in wil_request_firmware()
679 if (rc1 < 0) { in wil_request_firmware()
680 rc = rc1; in wil_request_firmware()
683 rc = wil_fw_process(wil, d, rc1, load); in wil_request_firmware()
Ddebugfs.c1024 int rc, rc1; in wil_write_file_wmi() local
1042 rc1 = wmi_send(wil, cmdid, vif->mid, cmd, cmdlen); in wil_write_file_wmi()
1045 wil_info(wil, "0x%04x[%d] -> %d\n", cmdid, cmdlen, rc1); in wil_write_file_wmi()
/Linux-v5.4/drivers/net/ethernet/ibm/
Dibmveth.c769 int rc1 = 0, rc2 = 0; in ibmveth_set_csum_offload() local
834 rc1 = -EIO; in ibmveth_set_csum_offload()
836 rc1 = -EIO; in ibmveth_set_csum_offload()
845 return rc1 ? rc1 : rc2; in ibmveth_set_csum_offload()
853 int rc1 = 0, rc2 = 0; in ibmveth_set_tso() local
887 rc1 = -EIO; in ibmveth_set_tso()
907 return rc1 ? rc1 : rc2; in ibmveth_set_tso()
916 int rc1 = 0, rc2 = 0; in ibmveth_set_features() local
919 rc1 = ibmveth_set_csum_offload(dev, rx_csum); in ibmveth_set_features()
920 if (rc1 && !adapter->rx_csum) in ibmveth_set_features()
[all …]
/Linux-v5.4/Documentation/translations/ko_KR/
Dhowto.rst260 - 2주 후에 -rc1 커널이 릴리즈되며 여기서부터의 주안점은 새로운 커널을
265 드라이버(혹은 파일시스템)는 -rc1 이후에만 받아들여진다는 것을 기억해라.
268 있지 않기 때문이다. -rc1이 배포된 이후에 git를 사용하여 패치들을 Linus에게
/Linux-v5.4/drivers/char/tpm/
Dtpm_ibmvtpm.c598 int rc = -ENOMEM, rc1; in tpm_ibmvtpm_probe() local
676 rc1 = plpar_hcall_norets(H_FREE_CRQ, vio_dev->unit_address); in tpm_ibmvtpm_probe()
677 } while (rc1 == H_BUSY || H_IS_LONG_BUSY(rc1)); in tpm_ibmvtpm_probe()
/Linux-v5.4/Documentation/translations/ja_JP/
Dhowto.rst275 - 2週間後、-rc1 カーネルがリリースされ、この後にはカーネル全体の安定
278 -rc1 の後で受け付けられることもあることを覚えておいてください。な
280 ない限り、退行のリスクは無いからです。-rc1 がリリースされた後、
/Linux-v5.4/drivers/staging/qlge/
DTODO4 * commit 7c734359d350 ("qlge: Size RX buffers based on MTU.", v2.6.33-rc1)
23 18c49b91777c ("qlge: do vlan cleanup", v3.1-rc1), 8 years ago).
/Linux-v5.4/Documentation/networking/
Dnetdev-FAQ.rst46 merge window is closed, and it is called/tagged ``-rc1``. No new
47 features get mainlined after this -- only fixes to the rc1 content are
48 expected. After roughly a week of collecting fixes to the rc1 content,
67 Shortly after the two weeks have passed (and vX.Y-rc1 is released), the
90 and note the top of the "tags" section. If it is rc1, it is early in
/Linux-v5.4/Documentation/dev-tools/
Dubsan.rst22 CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.0-rc1+ #26
/Linux-v5.4/drivers/net/ethernet/hisilicon/hns/
Dhns_ethtool.c782 int rc1, rc2; in hns_set_coalesce() local
796 rc1 = ops->set_coalesce_usecs(priv->ae_handle, in hns_set_coalesce()
803 if (rc1 || rc2) in hns_set_coalesce()
/Linux-v5.4/Documentation/gpu/
Dintroduction.rst97 with the -rc1 release) are allowed. No new platform enabling or new drivers are
/Linux-v5.4/drivers/input/touchscreen/
Dcyttsp4_core.c1606 int rc1; in cyttsp4_startup_() local
1609 rc1 = cyttsp4_adap_read(cd, CY_REG_BASE, sizeof(ldr_err_app), in cyttsp4_startup_()
1611 if (rc1) { in cyttsp4_startup_()
1612 dev_err(cd->dev, "%s: Fail read r=%d\n", __func__, rc1); in cyttsp4_startup_()
/Linux-v5.4/net/smc/
Daf_smc.c1655 int rc1 = 0; in smc_shutdown() local
1692 rc1 = kernel_sock_shutdown(smc->clcsock, how); in smc_shutdown()
1698 return rc ? rc : rc1; in smc_shutdown()
/Linux-v5.4/drivers/s390/net/
Dqeth_core_main.c1449 int rc1 = 0, rc2 = 0, rc3 = 0; in qeth_halt_channels() local
1452 rc1 = qeth_halt_channel(card, &card->read); in qeth_halt_channels()
1455 if (rc1) in qeth_halt_channels()
1456 return rc1; in qeth_halt_channels()
1464 int rc1 = 0, rc2 = 0, rc3 = 0; in qeth_clear_channels() local
1467 rc1 = qeth_clear_channel(card, &card->read); in qeth_clear_channels()
1470 if (rc1) in qeth_clear_channels()
1471 return rc1; in qeth_clear_channels()
/Linux-v5.4/Documentation/process/
D2.Process.rst53 be called 2.6.40-rc1. The -rc1 release is the signal that the time to
78 February 11 4.16-rc1, merge window closes
Dhowto.rst256 - After two weeks a -rc1 kernel is released and the focus is on making the
261 after -rc1 because there is no risk of causing regressions with such a
264 patches to Linus after -rc1 is released, but the patches need to also be
/Linux-v5.4/Documentation/translations/it_IT/process/
Dhowto.rst265 - Al termine delle due settimane un kernel -rc1 viene rilasciato e
271 accettato dopo la -rc1 poiché non esistono rischi di una possibile
275 la -rc1 è stata rilasciata, ma è anche necessario inviare le patch ad

12