| /openbmc/qemu/docs/devel/ |
| H A D | stable-process.rst | 3 QEMU and the stable process
6 QEMU stable releases
9 QEMU stable releases are based upon the last released QEMU version
14 Usually, stable releases are only provided for the last major QEMU
16 stable releases are produced only until QEMU 2.12.0 is released, at
17 which point the stable process moves to producing 2.12.x/2.12.x.y releases.
19 What should go into a stable release?
22 Generally, the following patches are considered stable material:
30 for stable.
33 How to get a patch into QEMU stable
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | stable-kernel-rules.rst | 3 Everything you ever wanted to know about Linux -stable releases
7 "-stable" tree:
34 Procedure for submitting patches to the -stable tree
39 Security patches should not be handled (solely) by the -stable review
43 There are three options to submit a change to -stable trees:
45 1. Add a 'stable tag' to the description of a patch you then submit for
47 2. Ask the stable team to pick up a patch already mainlined.
48 3. Submit a patch to the stable team that is equivalent to a change already
60 stable series. When doing so, ensure the fix or an equivalent is applicable,
61 submitted, or already present in all newer stable trees still supported. This is
[all …]
|
| 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
101 Stable Kernel Source Interfaces
140 stable source interface, a new interface would have been created, and
|
| H A D | applying-patches.rst | 248 The 5.x.y (-stable) and 5.x patches live at
261 The stable -rc patches live at
263 https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/
269 These are the base stable releases released by Linus. The highest numbered
272 If regressions or other serious flaws are found, then a -stable fix patch
304 Kernels with 3-digit versions are -stable kernels. They contain small(ish)
308 This is the recommended branch for users who want the most recent stable
313 the current stable kernel.
315 The -stable team provides normal as well as incremental patches. Below is
341 of base 5.x kernel, they are applied on top of previous stable kernel
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/xmlrpc-c/xmlrpc-c/ |
| H A D | 0001-unix-common.mk-Ensuring-Sequential-Execution-of-rm-a.patch | 31 martin@jama /OE/build/oe-core/tmp/work/core2-64-oe-linux/xmlrpc-c/1.60.03/git/stable $ grep -A 1 li…
32 make -C libutil++/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/xmlrpc-c/1.60.03/git/stable/lib/…
35 …-linux/xmlrpc-c/1.60.03/git/stable/lib/libutil++/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/…
38 martin@jama /OE/build/oe-core/tmp/work/core2-64-oe-linux/xmlrpc-c/1.60.03/git/stable $ grep -A 1 li…
39 make -C libutil/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/xmlrpc-c/1.60.03/git/stable/lib/li…
42 …e-linux/xmlrpc-c/1.60.03/git/stable/lib/libutil/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/x…
45 …e-linux/xmlrpc-c/1.60.03/git/stable/lib/libutil/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/x…
48 …e-linux/xmlrpc-c/1.60.03/git/stable/lib/libutil/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/x…
51 …e-linux/xmlrpc-c/1.60.03/git/stable/lib/libutil/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/x…
54 …e-linux/xmlrpc-c/1.60.03/git/stable/lib/libutil/ -f /OE/build/oe-core/tmp/work/core2-64-oe-linux/x…
[all …]
|
| /openbmc/linux/Documentation/translations/ja_JP/ |
| H A D | stable_kernel_rules.txt | 2 This is Japanese translated version of "Documentation/process/stable-kernel-rules.rst".
15 linux-2.6.29/Documentation/process/stable-kernel-rules.rst
28 ずっと知りたかった Linux 2.6 -stable リリースの全て
30 "-stable" ツリーにどのような種類のパッチが受け入れられるか、どのような
48 Linus のツリーでのコミットID を -stable へのパッチ投稿の際に引用す
51 -stable ツリーにパッチを送付する手続き-
53 - 上記の規則に従っているかを確認した後に、stable@vger.kernel.org にパッチ
59 メンテナーによるレビューのために -stable キューに追加される。
60 - パッチに stable@vger.kernel.org のアドレスが付加されているときには、それ
61 が Linus のツリーに入る時に自動的に stable チームに email される。
[all …]
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | stable-kernel-rules.rst | 3 :Original: :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
8 Tutto quello che volevate sapere sui rilasci -stable di Linux
12 "-stable":
41 Procedura per sottomettere patch per i sorgenti -stable
46 di revisione -stable, ma dovrebbe seguire le procedure descritte in
62 Cc: stable@vger.kernel.org
74 stable@vger.kernel.org includendo: il titolo della patch, l'identificativo
84 precedenza, a stable@vger.kernel.org. Dovete annotare nel changelog
121 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
122 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
[all …]
|
| /openbmc/libpldm/ |
| H A D | README.md | 59 1. Stable
64 stable category. However, this may not always be possible. What to do when
68 ### What does it mean to mark a function as stable?
70 Marking a function as stable makes the following promise to users of the
78 Marking a function as stable does _not_ promise that it is free of
82 Given this, it is always okay to implement functions marked stable in terms of
98 Testing --> Stable: Stabilise
99 Stable --> Deprecated: Deprecate
109 | Production | `-Dabi=deprecated,stable` |
110 | Maintenance | `-Dabi=stable` |
[all …]
|
| /openbmc/linux/rust/alloc/vec/ |
| H A D | partial_eq.rs | 25 __impl_slice_eq1! { [A1: Allocator, A2: Allocator] Vec<T, A1>, Vec<U, A2>, #[stable(feature = "rust…
26 __impl_slice_eq1! { [A: Allocator] Vec<T, A>, &[U], #[stable(feature = "rust1", since = "1.0.0")] }
27 __impl_slice_eq1! { [A: Allocator] Vec<T, A>, &mut [U], #[stable(feature = "rust1", since = "1.0.0"…
28 __impl_slice_eq1! { [A: Allocator] &[T], Vec<U, A>, #[stable(feature = "partialeq_vec_for_ref_slice…
29 __impl_slice_eq1! { [A: Allocator] &mut [T], Vec<U, A>, #[stable(feature = "partialeq_vec_for_ref_s…
30 __impl_slice_eq1! { [A: Allocator] Vec<T, A>, [U], #[stable(feature = "partialeq_vec_for_slice", si…
31 __impl_slice_eq1! { [A: Allocator] [T], Vec<U, A>, #[stable(feature = "partialeq_vec_for_slice", si…
33 __impl_slice_eq1! { [A: Allocator] Cow<'_, [T]>, Vec<U, A> where T: Clone, #[stable(feature = "rust…
35 __impl_slice_eq1! { [] Cow<'_, [T]>, &[U] where T: Clone, #[stable(feature = "rust1", since = "1.0.…
37 __impl_slice_eq1! { [] Cow<'_, [T]>, &mut [U] where T: Clone, #[stable(feature = "rust1", since = "…
[all …]
|
| H A D | drain.rs | 23 #[stable(feature = "drain", since = "1.6.0")]
38 #[stable(feature = "collection_debug", since = "1.17.0")]
58 #[stable(feature = "vec_drain_as_slice", since = "1.46.0")]
141 #[stable(feature = "vec_drain_as_slice", since = "1.46.0")]
148 #[stable(feature = "drain", since = "1.6.0")]
150 #[stable(feature = "drain", since = "1.6.0")]
153 #[stable(feature = "drain", since = "1.6.0")]
167 #[stable(feature = "drain", since = "1.6.0")]
175 #[stable(feature = "drain", since = "1.6.0")]
244 #[stable(feature = "drain", since = "1.6.0")]
[all …]
|
| H A D | into_iter.rs | 33 #[stable(feature = "rust1", since = "1.0.0")]
51 #[stable(feature = "vec_intoiter_debug", since = "1.13.0")]
70 #[stable(feature = "vec_into_iter_as_slice", since = "1.15.0")]
88 #[stable(feature = "vec_into_iter_as_slice", since = "1.15.0")]
173 #[stable(feature = "vec_intoiter_as_ref", since = "1.46.0")]
180 #[stable(feature = "rust1", since = "1.0.0")]
182 #[stable(feature = "rust1", since = "1.0.0")]
185 #[stable(feature = "rust1", since = "1.0.0")]
296 #[stable(feature = "rust1", since = "1.0.0")]
334 #[stable(feature = "rust1", since = "1.0.0")]
[all …]
|
| /openbmc/linux/rust/alloc/collections/ |
| H A D | mod.rs | 5 #![stable(feature = "rust1", since = "1.0.0")]
17 #[stable(feature = "rust1", since = "1.0.0")]
20 #[stable(feature = "rust1", since = "1.0.0")]
25 #[stable(feature = "rust1", since = "1.0.0")]
28 #[stable(feature = "rust1", since = "1.0.0")]
33 #[stable(feature = "rust1", since = "1.0.0")]
38 #[stable(feature = "rust1", since = "1.0.0")]
43 #[stable(feature = "rust1", since = "1.0.0")]
48 #[stable(feature = "rust1", since = "1.0.0")]
53 #[stable(feature = "rust1", since = "1.0.0")]
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
| H A D | cve-exclusion_6.12.inc | 5411 CVE_STATUS[CVE-2023-28746] = "cpe-stable-backport: Backported in 6.6.22"
5687 CVE_STATUS[CVE-2023-46838] = "cpe-stable-backport: Backported in 6.6.14"
5691 CVE_STATUS[CVE-2023-47233] = "cpe-stable-backport: Backported in 6.6.24"
5699 CVE_STATUS[CVE-2023-50431] = "cpe-stable-backport: Backported in 6.6.14"
5709 CVE_STATUS[CVE-2023-51779] = "cpe-stable-backport: Backported in 6.6.9"
5713 CVE_STATUS[CVE-2023-51780] = "cpe-stable-backport: Backported in 6.6.8"
5715 CVE_STATUS[CVE-2023-51781] = "cpe-stable-backport: Backported in 6.6.8"
5717 CVE_STATUS[CVE-2023-51782] = "cpe-stable-backport: Backported in 6.6.8"
5723 CVE_STATUS[CVE-2023-52429] = "cpe-stable-backport: Backported in 6.6.18"
5727 CVE_STATUS[CVE-2023-52434] = "cpe-stable-backport: Backported in 6.6.8"
[all …]
|
| H A D | cve-exclusion_6.6.inc | 5411 CVE_STATUS[CVE-2023-28746] = "cpe-stable-backport: Backported in 6.6.22"
5687 CVE_STATUS[CVE-2023-46838] = "cpe-stable-backport: Backported in 6.6.14"
5691 CVE_STATUS[CVE-2023-47233] = "cpe-stable-backport: Backported in 6.6.24"
5699 CVE_STATUS[CVE-2023-50431] = "cpe-stable-backport: Backported in 6.6.14"
5709 CVE_STATUS[CVE-2023-51779] = "cpe-stable-backport: Backported in 6.6.9"
5713 CVE_STATUS[CVE-2023-51780] = "cpe-stable-backport: Backported in 6.6.8"
5715 CVE_STATUS[CVE-2023-51781] = "cpe-stable-backport: Backported in 6.6.8"
5717 CVE_STATUS[CVE-2023-51782] = "cpe-stable-backport: Backported in 6.6.8"
5723 CVE_STATUS[CVE-2023-52429] = "cpe-stable-backport: Backported in 6.6.18"
5727 CVE_STATUS[CVE-2023-52434] = "cpe-stable-backport: Backported in 6.6.8"
[all …]
|
| H A D | cve-exclusion_6.10.inc | 5411 CVE_STATUS[CVE-2023-28746] = "cpe-stable-backport: Backported in 6.6.22"
5687 CVE_STATUS[CVE-2023-46838] = "cpe-stable-backport: Backported in 6.6.14"
5691 CVE_STATUS[CVE-2023-47233] = "cpe-stable-backport: Backported in 6.6.24"
5699 CVE_STATUS[CVE-2023-50431] = "cpe-stable-backport: Backported in 6.6.14"
5709 CVE_STATUS[CVE-2023-51779] = "cpe-stable-backport: Backported in 6.6.9"
5713 CVE_STATUS[CVE-2023-51780] = "cpe-stable-backport: Backported in 6.6.8"
5715 CVE_STATUS[CVE-2023-51781] = "cpe-stable-backport: Backported in 6.6.8"
5717 CVE_STATUS[CVE-2023-51782] = "cpe-stable-backport: Backported in 6.6.8"
5723 CVE_STATUS[CVE-2023-52429] = "cpe-stable-backport: Backported in 6.6.18"
5727 CVE_STATUS[CVE-2023-52434] = "cpe-stable-backport: Backported in 6.6.8"
[all …]
|
| /openbmc/linux/Documentation/ABI/ |
| H A D | README | 12 stable/
14 defined to be stable. Userspace programs are free to use these
21 This directory documents interfaces that are felt to be stable,
28 be marked stable. Programs that use these interfaces are
71 Interfaces in stable may move to obsolete, as long as the proper
77 Interfaces in the testing state can move to the stable state when the
86 stable:
95 itself. See Documentation/process/stable-api-nonsense.rst.
|
| /openbmc/linux/rust/alloc/ |
| H A D | slice.rs | 12 #![stable(feature = "rust1", since = "1.0.0")]
46 #[stable(feature = "inherent_ascii_escape", since = "1.60.0")]
48 #[stable(feature = "slice_get_slice", since = "1.28.0")]
50 #[stable(feature = "from_ref", since = "1.28.0")]
54 #[stable(feature = "rust1", since = "1.0.0")]
56 #[stable(feature = "rust1", since = "1.0.0")]
58 #[stable(feature = "chunks_exact", since = "1.31.0")]
60 #[stable(feature = "rust1", since = "1.0.0")]
64 #[stable(feature = "rust1", since = "1.0.0")]
66 #[stable(feature = "rchunks", since = "1.31.0")]
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | ksm.rst | 22 KSM maintains reverse mapping information for KSM pages in the stable
26 the node of the stable tree that represents such KSM page points to a
28 KSM page points to the stable tree node.
31 the stable tree. The tree node becomes a "chain" that links one or
40 This way the stable tree lookup computational complexity is unaffected
43 stable tree itself.
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | release-process.rst | 4 Yocto Project Releases and the Stable Release Process
45 Realize that there can be patches merged onto the stable release
70 Stable Release Process
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
[all …]
|
| /openbmc/linux/drivers/parisc/ |
| H A D | pdc_stable.c | 3 * Interfaces to retrieve and set PDC Stable options (firmware)
8 * "A minimum of 96 bytes of Stable Storage is required. Providing more than
9 * 96 bytes of Stable Storage is optional [...]. Failure to provide the
15 * following code can deal with just 96 bytes of Stable Storage, and all
62 #define PDCS_PREFIX "PDC Stable Storage"
75 MODULE_DESCRIPTION("sysfs interface to HP PDC Stable Storage data");
79 /* holds Stable Storage size. Initialized once and for all, no lock needed */
89 unsigned long addr; /* entry address in stable storage */
130 * The general idea is that you don't read from the Stable Storage every time
132 * content of the stable storage WRT various paths in these structs. We read
[all …]
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | releases.md | 3 The Yocto Project releases twice a year (April and October): "stable" releases are made every six m…
5 …stable”, and only take bug fixes or security-critical upgrades. Active development occurs on the m…
8 …stable software platform for software to be developed, tested, and released. Also, the single bran…
22 …lopment branches at any given time: master and the most recent Long Term Stable (LTS) as the named…
|
| /openbmc/linux/mm/ |
| H A D | ksm.c | 70 * Therefore KSM uses two data structures - the stable and the unstable tree.
72 * The stable tree holds pointers to all the merged pages (ksm pages), sorted
75 * and therefore this tree is called the stable tree.
77 * The stable tree node includes information required for reverse
81 * KSM maintains two types of nodes in the stable tree:
92 * In addition to the stable tree, KSM uses a second data structure called the
110 * 4) KSM never flushes the stable tree, which means that even if it were to
112 * it is secured in the stable tree. (When we scan a new page, we first
113 * compare it against the stable tree, and then against the unstable tree.)
116 * stable trees and multiple unstable trees: one of each for each NUMA node.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | abi-stable.rst | 1 ABI stable symbols
4 Documents the interfaces that the developer has defined to be stable.
13 .. kernel-abi:: ABI/stable
|
| /openbmc/openbmc/poky/meta/recipes-devtools/log4cplus/ |
| H A D | log4cplus_2.1.2.bb | 10 SRC_URI = "${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}-stable/${PV}/${BP}.tar.gz \
14 UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/"
15 UPSTREAM_CHECK_REGEX = "log4cplus-stable/(?P<pver>\d+(\.\d+)+)/"
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/libpldm/ |
| H A D | libpldm_git.bb | 8 LIBPLDM_ABI_DEVELOPMENT = "deprecated,stable,testing"
9 LIBPLDM_ABI_MAINTENANCE = "stable,testing"
10 LIBPLDM_ABI_PRODUCTION = "deprecated,stable"
|