| /linux-6.1.9/Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 37 Greg提供了以下内容。对于一个含有drivers/char中混杂事项、将应用于4.15-rc1内核的
38 拉取请求，可以命名为 ``char-misc-4.15-rc1`` 。如果要在 ``char-misc-next`` 分支
41 git tag -s char-misc-4.15-rc1 char-misc-next
43 这将在 ``char-misc-next`` 分支的最后一个提交上创建一个名为 ``char-misc-4.15-rc1``
79 Char/Misc patches for 4.15-rc1
81 Here is the big char/misc patch set for the 4.15-rc1 merge window.
111 git push origin char-misc-4.15-rc1
121 …-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-misc-4.15-rc1
125 此命令要求git比较从“char-misc-4.15-rc1”标记位置到“master”分支头（上述
130 如果char-misc-4.15-rc1标记没有出现在我要求拉取的仓库中，git会提醒
[all …]
|
| D | rebasing-and-merging.rst | 159 git merge v5.2-rc1^0
|
| D | maintainer-entry-profile.rst | 51 提交者常常会误以为补丁可以在合并窗口关闭之前的任何时间发送，且下一个-rc1时仍
|
| /linux-6.1.9/Documentation/translations/zh_CN/admin-guide/ |
| D | reporting-regressions.rst | 40 #regzbot introduced v5.13..v5.14-rc1
102 #regzbot introduced: v5.13..v5.14-rc1
105 然正常，而Linux 5.14-rc1是首个您遇到问题的版本。如果你执行了二分以查找导致回
230 小提示：如果人们在每个开发周期中定期给出主线预发布（即v5.15-rc1或-rc3）以供
231 测试，则可以避免这种情况。为了更好地解释，可以设想一个在Linux v5.14和v5.15-rc1
232 之间集成的更改，该更改导致了回归，但同时是应用于5.15-rc1的其他改进的强依赖。
|
| /linux-6.1.9/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 …]
|
| /linux-6.1.9/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 …]
|
| D | messy-diffstat.rst | 23 ... vM --- vN-rc1 --- vN-rc2 --- vN-rc3 --- ... --- vN-rc7 --- vN
38 ... vM --- vN-rc1 --- vN-rc2 --- vN-rc3 --- ... --- vN-rc7 --- vN
48 ... vM --- vN-rc1 --- vN-rc2 --- vN-rc3 --- ... --- vN-rc7 --- vN
54 Our maintainer has created one branch at vN-rc1 and another at vN-rc2; the
63 starts at vN-rc1, it may end up including all of the changes between there
80 ... vM --- vN-rc1 --- vN-rc2 --- vN-rc3 --- ... --- vN-rc7 --- vN
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-tsl2772 | 2 KernelVersion: 3.3-rc1
9 KernelVersion: 3.3-rc1
|
| /linux-6.1.9/Documentation/translations/zh_CN/process/ |
| D | 2.Process.rst | 52 将被称为5.6-rc1。-rc1 版本是一个信号，表示合并新特性的时间已经过去，稳定下一
69 九月 30 5.4-rc1 合并窗口关闭
|
| D | howto.rst | 216 - 两个星期以后-rc1版本内核发布。之后只有不包含可能影响整个内核稳定性的
218 可能在-rc1后被接受是因为这样的修改完全独立，不会影响其他的代码，所以
219 没有造成内核退步的风险。在-rc1以后也可以用git向Linus提交补丁，不过所
|
| /linux-6.1.9/Documentation/translations/zh_TW/process/ |
| D | 2.Process.rst | 55 將被稱爲5.6-rc1。-rc1 版本是一個信號，表示合併新特性的時間已經過去，穩定下一
72 九月 30 5.4-rc1 合併窗口關閉
|
| D | howto.rst | 219 - 兩個星期以後-rc1版本內核發布。之後只有不包含可能影響整個內核穩定性的
221 可能在-rc1後被接受是因爲這樣的修改完全獨立，不會影響其他的代碼，所以
222 沒有造成內核退步的風險。在-rc1以後也可以用git向Linus提交補丁，不過所
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/drivers/net/ethernet/ibm/ |
| D | ibmveth.c | 797 int rc1 = 0, rc2 = 0; in ibmveth_set_csum_offload() local
862 rc1 = -EIO; in ibmveth_set_csum_offload()
864 rc1 = -EIO; in ibmveth_set_csum_offload()
873 return rc1 ? rc1 : rc2; in ibmveth_set_csum_offload()
881 int rc1 = 0, rc2 = 0; in ibmveth_set_tso() local
915 rc1 = -EIO; in ibmveth_set_tso()
935 return rc1 ? rc1 : rc2; in ibmveth_set_tso()
944 int rc1 = 0, rc2 = 0; in ibmveth_set_features() local
947 rc1 = ibmveth_set_csum_offload(dev, rx_csum); in ibmveth_set_features()
948 if (rc1 && !adapter->rx_csum) in ibmveth_set_features()
[all …]
|
| /linux-6.1.9/Documentation/translations/ko_KR/ |
| D | howto.rst | 268 - 2주 후에 -rc1 커널이 릴리즈되며 여기서부터의 주안점은 새로운 커널을
273 드라이버(혹은 파일시스템)는 -rc1 이후에만 받아들여진다는 것을 기억해라.
276 있지 않기 때문이다. -rc1이 배포된 이후에 git를 사용하여 패치들을 Linus에게
|
| /linux-6.1.9/drivers/char/tpm/ |
| D | tpm_ibmvtpm.c | 605 int rc = -ENOMEM, rc1; in tpm_ibmvtpm_probe() local
706 rc1 = plpar_hcall_norets(H_FREE_CRQ, vio_dev->unit_address); in tpm_ibmvtpm_probe()
707 } while (rc1 == H_BUSY || H_IS_LONG_BUSY(rc1)); in tpm_ibmvtpm_probe()
|
| /linux-6.1.9/Documentation/translations/ja_JP/ |
| D | howto.rst | 283 - 2週間後、-rc1 カーネルがリリースされ、この後にはカーネル全体の安定
286 -rc1 の後で受け付けられることもあることを覚えておいてください。な
288 ない限り、退行のリスクは無いからです。-rc1 がリリースされた後、
|
| /linux-6.1.9/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
|
| /linux-6.1.9/net/smc/ |
| D | smc_close.c | 201 int rc1 = 0; in smc_close_active() local
243 rc1 = kernel_sock_shutdown(smc->clcsock, in smc_close_active()
245 rc = rc ? rc : rc1; in smc_close_active()
|
| /linux-6.1.9/Documentation/ABI/removed/ |
| D | sysfs-kernel-uids | 2 Date: December 2007, finally removed in kernel v2.6.34-rc1
|