| /openbmc/linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | reporting-issues.rst | 31 `Linux穩定版郵件列表 <https://lore.kernel.org/stable/>`_ 存檔中匹配的報告並
33 報告給穩定版郵件列表（stable@vger.kernel.org）。
154 * 檢查 `Linux穩定版郵件列表 <https://lore.kernel.org/stable/>`_ 中的現有報告。
160 * 向Linux穩定版郵件列表發送一個簡短的問題報告(stable@vger.kernel.org)。大致
1154 版郵件列表的檔案 <https://lore.kernel.org/stable/>`_ 中搜索類似問題的報告。
1177 *向Linux穩定版郵件列表發送一個簡短的問題報告(stable@vger.kernel.org)。
1211 「Documentation/translations/zh_TW/process/stable-kernel-rules.rst」中所列出的
1253 Cc: <stable@vger.kernel.org> # 5.4+
1283 以及穩定版郵件列表（stable@vger.kernel.org）。
|
| /openbmc/qemu/ |
| H A D | .readthedocs.yml | 3 # See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
19 # https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
|
| /openbmc/linux/Documentation/translations/zh_CN/process/ |
| H A D | index.rst | 45 stable-api-nonsense
46 stable-kernel-rules
|
| H A D | howto.rst | 117 :ref:`Documentation/translations/zh_CN/process/stable-api-nonsense.rst <cn_stable_api_nonsense>`
138 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
261 由3个数字组成的内核版本号说明此内核是-stable版本。它们包含内核的相对较小且
267 稳定版内核树版本由“稳定版”小组（邮件地址<stable@vger.kernel.org>）维护，一般
270 内核源码中的 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
|
| H A D | 5.Posting.rst | 222 补丁副本也应发到stable@vger.kernel.org 。另外，在补丁本身的标签中添加一个
223 “Cc: stable@vger.kernel.org”；这将使稳定版团队在修复进入主线时收到通知。
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | rotary-encoder.rst | 15 Some encoders have both outputs low in stable states, others also have
16 a stable state with both outputs high (half-period mode) and some have
17 a stable state in all steps (quarter-period mode).
50 rotational direction based on the last stable state. Events are reported in
51 states b) and d) given that the new stable state is different from the last
|
| /openbmc/linux/Documentation/translations/zh_TW/process/ |
| H A D | howto.rst | 120 :ref:`Documentation/translations/zh_TW/process/stable-api-nonsense.rst <tw_stable_api_nonsense>`
141 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
264 由3個數字組成的內核版本號說明此內核是-stable版本。它們包含內核的相對較小且
270 穩定版內核樹版本由「穩定版」小組（郵件地址<stable@vger.kernel.org>）維護，一般
273 內核源碼中的 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
|
| H A D | index.rst | 47 stable-api-nonsense
48 stable-kernel-rules
|
| /openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
| H A D | reporting-issues.rst | 23 `Linux稳定版邮件列表 <https://lore.kernel.org/stable/>`_ 存档中匹配的报告并
25 请报告给稳定版邮件列表（stable@vger.kernel.org）并抄送回归邮件列表
149 * 检查 `Linux稳定版邮件列表 <https://lore.kernel.org/stable/>`_ 中的现有报告。
155 * 向Linux稳定版邮件列表发送一个简短的问题报告（stable@vger.kernel.org）并抄送
1156 版邮件列表的档案 <https://lore.kernel.org/stable/>`_ 中搜索类似问题的报告。
1179 *向Linux稳定版邮件列表发送一个简短的问题报告(stable@vger.kernel.org)并
1219 Documentation/translations/zh_CN/process/stable-kernel-rules.rst 中所列出的
1261 Cc: <stable@vger.kernel.org> # 5.4+
1291 以及稳定版邮件列表（stable@vger.kernel.org）。
|
| H A D | reporting-regressions.rst | 95 `Linux稳定版邮件列表 <https://lore.kernel.org/stable/>`_ （stable@vger.kernel.org）。
159 <http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/>`_ 。
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | abi-testing.rst | 4 Documents interfaces that are felt to be stable,
13 be marked stable.
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | ABI.rst | 7 I. Regarding stable bindings/ABI, we quote from the 2013 ARM mini-summit
10 "That still leaves the question of, what does a stable binding look
11 like? Certainly a stable binding means that a newer kernel will not
|
| /openbmc/openbmc/poky/meta/recipes-devtools/rust/files/ |
| H A D | rustc-bootstrap.patch | 1 When rust.channel is set to either beta or stable, we can't use
3 to use nightly features on stable or beta.
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/ |
| H A D | systemd.inc | 19 SRCBRANCH = "v255-stable"
20 SRC_URI = "git://github.com/systemd/systemd-stable.git;protocol=https;branch=${SRCBRANCH}"
|
| /openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-security/bastille/files/ |
| H A D | organize_distro_discovery.patch | 187 - $stable="3.1"; #Change this when Debian stable changes
191 - print STDERR "$err System is not running a stable Debian GNU/Linux version. Setting to $stable.\…
192 - $distro="DB$stable";
245 + $stable="3.1"; #Change this when Debian stable changes
249 + print STDERR "$err System is not running a stable Debian GNU/Linux version. Setting to $sta…
250 + $distro="DB$stable";
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/ |
| H A D | 03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch | 11 …r custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/mark.html
18 1. https://docs.pytest.org/en/stable/mark.html
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/minifi-cpp/files/ |
| H A D | 0008-libsodium-aarch64_crypto.patch | 11 --- a/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aes256gcm/armcrypto/aead_aes256gcm_armc…
12 +++ b/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aes256gcm/armcrypto/aead_aes256gcm_armc…
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | release-process.rst | 45 Realize that there can be patches merged onto the stable release
73 Once released, the release enters the stable release process at which
74 time a person is assigned as the maintainer for that stable release.
79 stable release.
85 not backported to a stable release. This policy means generic recipe
95 While stable releases are supported for a duration of seven months,
100 fixes not only for the current stable release, but also to the
101 :term:`LTS` releases that are still supported. Older stable releases which
115 of stable and :term:`LTS` releases.
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | base.yml | 3 # On stable branches this is changed by later rules. Should also
19 # For pipelines running for stable "staging-X.Y" branches
36 # Never run jobs upstream on stable branch, staging branch jobs already ran
37 - if: '$CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM && $CI_COMMIT_BRANCH =~ /^stable-/'
|
| /openbmc/openbmc/poky/meta/recipes-support/libevent/libevent/ |
| H A D | Makefile-missing-test-dir.patch | 16 diff --git a/libevent-2.1.8-stable/test/include.am b/libevent-2.1.8-stable/test/include.am
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | firewire.rst | 22 .. include:: ../ABI/stable/firewire-cdev
31 .. include:: ../ABI/stable/sysfs-bus-firewire
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | maintainer-profile.rst | 20 be queued in mm-stable [3]_ , and finally pull-requested to the mainline by the
45 mm-stable[3] trees depend on the memory management subsystem maintainer.
58 .. [3] https://git.kernel.org/akpm/mm/h/mm-stable
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | index.rst | 45 stable-api-nonsense
47 stable-kernel-rules
|
| /openbmc/linux/Documentation/process/ |
| H A D | stable-api-nonsense.rst | 11 kernel interface, nor does it have a stable kernel interface**.
19 the syscall interface. That interface is **very** stable over time, and
23 on being stable.
28 You think you want a stable kernel interface, but you really do not, and
29 you don't even know it. What you want is a stable running driver, and
32 tree, all of which has made Linux into such a strong, stable, and mature
53 So, there are two main topics here, binary kernel interfaces and stable
60 Assuming that we had a stable kernel source interface for the kernel, a
140 stable source interface, a new interface would have been created, and
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | cs4271.txt | 24 The CS4271 requires its LRCLK and MCLK to be stable before its RESET
33 Note that this is not needed in case the clocks are stable
|