| /Linux-v5.10/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 7 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 …]
|
| D | lpfc.rst | 20 The driver now requires a 2.6.12 (if pre-release, 2.6.12-rc1) or later
71 At this time, the driver requires the 2.6.12 (if pre-release, 2.6.12-rc1)
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-tsl2772 | 2 KernelVersion: 3.3-rc1
9 KernelVersion: 3.3-rc1
|
| /Linux-v5.10/Documentation/maintainer/ |
| D | pull-requests.rst | 36 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.10/drivers/ide/ |
| D | qd65xx.c | 427 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.10/arch/arm64/crypto/ |
| D | sha512-ce-core.S | 83 .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.10/Documentation/translations/zh_CN/process/ |
| D | 2.Process.rst | 45 将被称为4.14-rc1。RC1版本是一个信号，表示合并新特性的时间已经过去，稳定下一
62 二月 11 4.16-rc1, 合并窗口关闭
|
| D | howto.rst | 217 - 两个星期以后-rc1版本内核发布。之后只有不包含可能影响整个内核稳定性的
219 可能在-rc1后被接受是因为这样的修改完全独立，不会影响其他的代码，所以
220 没有造成内核退步的风险。在-rc1以后也可以用git向Linus提交补丁，不过所
|
| /Linux-v5.10/drivers/net/wireless/ath/wil6210/ |
| D | fw_inc.c | 649 int rc, rc1; in wil_request_firmware() local
666 for (sz = fw->size, d = fw->data; sz; sz -= rc1, d += rc1) { in wil_request_firmware()
667 rc1 = wil_fw_verify(wil, d, sz); in wil_request_firmware()
668 if (rc1 < 0) { in wil_request_firmware()
669 rc = rc1; in wil_request_firmware()
672 rc = wil_fw_process(wil, d, rc1, load); in wil_request_firmware()
|
| /Linux-v5.10/drivers/net/ethernet/ibm/ |
| D | ibmveth.c | 776 int rc1 = 0, rc2 = 0; in ibmveth_set_csum_offload() local
841 rc1 = -EIO; in ibmveth_set_csum_offload()
843 rc1 = -EIO; in ibmveth_set_csum_offload()
852 return rc1 ? rc1 : rc2; in ibmveth_set_csum_offload()
860 int rc1 = 0, rc2 = 0; in ibmveth_set_tso() local
894 rc1 = -EIO; in ibmveth_set_tso()
914 return rc1 ? rc1 : rc2; in ibmveth_set_tso()
923 int rc1 = 0, rc2 = 0; in ibmveth_set_features() local
926 rc1 = ibmveth_set_csum_offload(dev, rx_csum); in ibmveth_set_features()
927 if (rc1 && !adapter->rx_csum) in ibmveth_set_features()
[all …]
|
| /Linux-v5.10/Documentation/translations/ko_KR/ |
| D | howto.rst | 260 - 2주 후에 -rc1 커널이 릴리즈되며 여기서부터의 주안점은 새로운 커널을
265 드라이버(혹은 파일시스템)는 -rc1 이후에만 받아들여진다는 것을 기억해라.
268 있지 않기 때문이다. -rc1이 배포된 이후에 git를 사용하여 패치들을 Linus에게
|
| /Linux-v5.10/drivers/char/tpm/ |
| D | tpm_ibmvtpm.c | 610 int rc = -ENOMEM, rc1; in tpm_ibmvtpm_probe() local
703 rc1 = plpar_hcall_norets(H_FREE_CRQ, vio_dev->unit_address); in tpm_ibmvtpm_probe()
704 } while (rc1 == H_BUSY || H_IS_LONG_BUSY(rc1)); in tpm_ibmvtpm_probe()
|
| /Linux-v5.10/Documentation/translations/ja_JP/ |
| D | howto.rst | 275 - 2週間後、-rc1 カーネルがリリースされ、この後にはカーネル全体の安定
278 -rc1 の後で受け付けられることもあることを覚えておいてください。な
280 ない限り、退行のリスクは無いからです。-rc1 がリリースされた後、
|
| /Linux-v5.10/drivers/staging/qlge/ |
| D | TODO | 1 * commit 7c734359d350 ("qlge: Size RX buffers based on MTU.", v2.6.33-rc1)
20 18c49b91777c ("qlge: do vlan cleanup", v3.1-rc1), 8 years ago).
|
| /Linux-v5.10/tools/testing/kunit/test_data/ |
| D | test_kernel_panic_interrupt.log | 22 [ 0.060000] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| D | test_config_printk_time.log | 28 [ 0.060000] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| D | test_output_with_prefix_isolated_correctly.log | 29 [ 0.060000] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| D | test_pound_no_prefix.log | 30 CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| D | test_pound_sign.log | 30 [ 0.060000] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| D | test_multiple_prefixes.log | 28 [ 0.060000][ T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| D | test_interrupted_tap_output.log | 34 [ 0.060000] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc1-gea2dd7c0875e-dirty #2
|
| /Linux-v5.10/Documentation/ABI/removed/ |
| D | sysfs-kernel-uids | 2 Date: December 2007, finally removed in kernel v2.6.34-rc1
|
| /Linux-v5.10/Documentation/networking/ |
| D | netdev-FAQ.rst | 46 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.10/Documentation/dev-tools/ |
| D | ubsan.rst | 22 CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.0-rc1+ #26
|
| /Linux-v5.10/drivers/net/ethernet/hisilicon/hns/ |
| D | hns_ethtool.c | 782 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()
|
