/openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
H A D | cve-exclusion_6.12.inc | 15 CVE_STATUS[CVE-2004-0230] = "fixed-version: Fixed from version 3.6rc1" 37 CVE_STATUS[CVE-2008-7316] = "fixed-version: Fixed from version 2.6.25rc1" 49 CVE_STATUS[CVE-2010-5313] = "fixed-version: Fixed from version 2.6.38rc1" 53 CVE_STATUS[CVE-2010-5328] = "fixed-version: Fixed from version 2.6.35rc1" 55 CVE_STATUS[CVE-2010-5329] = "fixed-version: Fixed from version 2.6.39rc1" 59 CVE_STATUS[CVE-2010-5332] = "fixed-version: Fixed from version 2.6.37rc1" 61 CVE_STATUS[CVE-2011-4098] = "fixed-version: Fixed from version 3.2rc1" 63 CVE_STATUS[CVE-2011-4131] = "fixed-version: Fixed from version 3.3rc1" 65 CVE_STATUS[CVE-2011-4915] = "fixed-version: Fixed from version 3.2rc1" 71 CVE_STATUS[CVE-2011-5321] = "fixed-version: Fixed from version 3.2rc1" [all …]
|
H A D | cve-exclusion_6.6.inc | 15 CVE_STATUS[CVE-2004-0230] = "fixed-version: Fixed from version 3.6rc1" 37 CVE_STATUS[CVE-2008-7316] = "fixed-version: Fixed from version 2.6.25rc1" 49 CVE_STATUS[CVE-2010-5313] = "fixed-version: Fixed from version 2.6.38rc1" 53 CVE_STATUS[CVE-2010-5328] = "fixed-version: Fixed from version 2.6.35rc1" 55 CVE_STATUS[CVE-2010-5329] = "fixed-version: Fixed from version 2.6.39rc1" 59 CVE_STATUS[CVE-2010-5332] = "fixed-version: Fixed from version 2.6.37rc1" 61 CVE_STATUS[CVE-2011-4098] = "fixed-version: Fixed from version 3.2rc1" 63 CVE_STATUS[CVE-2011-4131] = "fixed-version: Fixed from version 3.3rc1" 65 CVE_STATUS[CVE-2011-4915] = "fixed-version: Fixed from version 3.2rc1" 71 CVE_STATUS[CVE-2011-5321] = "fixed-version: Fixed from version 3.2rc1" [all …]
|
H A D | cve-exclusion_6.10.inc | 15 CVE_STATUS[CVE-2004-0230] = "fixed-version: Fixed from version 3.6rc1" 37 CVE_STATUS[CVE-2008-7316] = "fixed-version: Fixed from version 2.6.25rc1" 49 CVE_STATUS[CVE-2010-5313] = "fixed-version: Fixed from version 2.6.38rc1" 53 CVE_STATUS[CVE-2010-5328] = "fixed-version: Fixed from version 2.6.35rc1" 55 CVE_STATUS[CVE-2010-5329] = "fixed-version: Fixed from version 2.6.39rc1" 59 CVE_STATUS[CVE-2010-5332] = "fixed-version: Fixed from version 2.6.37rc1" 61 CVE_STATUS[CVE-2011-4098] = "fixed-version: Fixed from version 3.2rc1" 63 CVE_STATUS[CVE-2011-4131] = "fixed-version: Fixed from version 3.3rc1" 65 CVE_STATUS[CVE-2011-4915] = "fixed-version: Fixed from version 3.2rc1" 71 CVE_STATUS[CVE-2011-5321] = "fixed-version: Fixed from version 3.2rc1" [all …]
|
/openbmc/linux/Documentation/translations/zh_CN/maintainer/ |
H A 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 …]
|
/openbmc/u-boot/board/compulab/cm_t3517/ |
H A D | cm_t3517.c | 196 int rc = 0, rc1 = 0; in board_eth_init() local 198 rc1 = cm_t3517_handle_mac_address(); in board_eth_init() 199 if (rc1) in board_eth_init() 202 rc1 = cm_t3517_init_emac(bis); in board_eth_init() 203 if (rc1 > 0) in board_eth_init() 206 rc1 = cl_omap3_smc911x_init(0, 4, CONFIG_SMC911X_BASE, in board_eth_init() 208 if (rc1 > 0) in board_eth_init()
|
/openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
H A 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的其他改进的强依赖。
|
/openbmc/linux/Documentation/scsi/ |
H A 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 …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/emlog/files/ |
H A D | 0001-emlog-Do-not-use-no_llseek-with-kernel-6.12.0.patch | 6 no_llseek is finally gone with 6.12-rc1 [1] 23 - .llseek = no_llseek, /* no_llseek by default introduced at v2.6.37-rc1 */ 25 + /* no_llseek by default introduced at v2.6.37-rc1 and
|
/openbmc/linux/Documentation/maintainer/ |
H A D | pull-requests.rst | 34 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named 35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch 38 git tag -s char-misc-4.15-rc1 char-misc-next 40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the 93 Char/Misc patches for 4.15-rc1 95 Here is the big char/misc patch set for the 4.15-rc1 merge window. 127 git push origin char-misc-4.15-rc1 139 …-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-misc-4.15-rc1 144 'char-misc-4.15-rc1' tag location, to the head of the 'master' 151 If the char-misc-4.15-rc1 tag is not present in the repo that I am [all …]
|
H A 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
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-iio-light-tsl2772 | 2 KernelVersion: 3.3-rc1 9 KernelVersion: 3.3-rc1
|
/openbmc/linux/Documentation/translations/zh_TW/process/ |
H A D | 2.Process.rst | 55 將被稱爲5.6-rc1。-rc1 版本是一個信號,表示合併新特性的時間已經過去,穩定下一 72 九月 30 5.4-rc1 合併窗口關閉
|
H A D | howto.rst | 219 - 兩個星期以後-rc1版本內核發布。之後只有不包含可能影響整個內核穩定性的 221 可能在-rc1後被接受是因爲這樣的修改完全獨立,不會影響其他的代碼,所以 222 沒有造成內核退步的風險。在-rc1以後也可以用git向Linus提交補丁,不過所
|
/openbmc/linux/Documentation/translations/zh_CN/process/ |
H A D | 2.Process.rst | 52 将被称为5.6-rc1。-rc1 版本是一个信号,表示合并新特性的时间已经过去,稳定下一 69 九月 30 5.4-rc1 合并窗口关闭
|
H A D | howto.rst | 216 - 两个星期以后-rc1版本内核发布。之后只有不包含可能影响整个内核稳定性的 218 可能在-rc1后被接受是因为这样的修改完全独立,不会影响其他的代码,所以 219 没有造成内核退步的风险。在-rc1以后也可以用git向Linus提交补丁,不过所
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-pandas/ |
H A D | 0001-pyproject.toml-Downgrade-numpy-version-needs-to-1.x.patch | 21 # Force numpy higher than 2.0rc1, so that built wheels are compatible 23 - "numpy>=2.0.0rc1",
|
H A D | 0001-pyproject.toml-don-t-pin-dependency-versions.patch | 32 # Force numpy higher than 2.0rc1, so that built wheels are compatible 34 "numpy>=2.0.0rc1",
|
/openbmc/linux/arch/arm64/crypto/ |
H A 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
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-crypto/libtomcrypt/ |
H A D | libtomcrypt_1.18.2.bb | 4 # Unlicense isn't very accurate for this revision, it was WTFPL in 0.18.0-rc1: 6 # then updated to dual license PD and WTFPL also in 0.18.0-rc1:
|
/openbmc/linux/drivers/net/wireless/ath/wil6210/ |
H A 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()
|
/openbmc/linux/drivers/net/ethernet/ibm/ |
H A D | ibmveth.c | 796 int rc1 = 0, rc2 = 0; in ibmveth_set_csum_offload() local 859 rc1 = -EIO; in ibmveth_set_csum_offload() 861 rc1 = -EIO; in ibmveth_set_csum_offload() 870 return rc1 ? rc1 : rc2; in ibmveth_set_csum_offload() 878 int rc1 = 0, rc2 = 0; in ibmveth_set_tso() local 910 rc1 = -EIO; in ibmveth_set_tso() 930 return rc1 ? rc1 : rc2; in ibmveth_set_tso() 939 int rc1 = 0, rc2 = 0; in ibmveth_set_features() local 942 rc1 = ibmveth_set_csum_offload(dev, rx_csum); in ibmveth_set_features() 943 if (rc1 && !adapter->rx_csum) in ibmveth_set_features() [all …]
|
/openbmc/u-boot/board/compulab/cm_t35/ |
H A D | cm_t35.c | 458 int rc = 0, rc1 = 0; in board_eth_init() local 460 rc1 = handle_mac_address(); in board_eth_init() 461 if (rc1) in board_eth_init() 464 rc1 = cl_omap3_smc911x_init(0, 5, CONFIG_SMC911X_BASE, in board_eth_init() 466 if (rc1 > 0) in board_eth_init() 469 rc1 = cl_omap3_smc911x_init(1, 4, SB_T35_SMC911X_BASE, NULL, -EINVAL); in board_eth_init() 470 if (rc1 > 0) in board_eth_init()
|
/openbmc/linux/drivers/char/tpm/ |
H A 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()
|
/openbmc/linux/Documentation/translations/ko_KR/ |
H A D | howto.rst | 268 - 2주 후에 -rc1 커널이 릴리즈되며 여기서부터의 주안점은 새로운 커널을 273 드라이버(혹은 파일시스템)는 -rc1 이후에만 받아들여진다는 것을 기억해라. 276 있지 않기 때문이다. -rc1이 배포된 이후에 git를 사용하여 패치들을 Linus에게
|
/openbmc/linux/Documentation/translations/ja_JP/ |
H A D | howto.rst | 282 - 2週間後 -rc1 カーネルがリリースされ、新しいカーネルを可能な限り堅牢に 287 -rc1 の後で受け付けられることもあることを覚えておいてください。な 289 ない限り、退行のリスクは無いからです。-rc1 がリリースされた後、
|