| /linux/scripts/gendwarfksyms/examples/ |
| H A D | kabi_ex.h | 7 * Examples for kABI stability features with --stable.
21 * ./gendwarfksyms --stable --dump-dies \
23 * FileCheck examples/kabi_ex.h --check-prefix=STABLE
26 * ./gendwarfksyms --stable --dump-versions \
48 * STABLE: variable structure_type s {
49 * STABLE-NEXT: }
64 * STABLE: variable enumeration_type e {
65 * STABLE-NEXT: enumerator A = 0 ,
66 * STABLE-NEXT: enumerator D = 123456789
67 * STABLE-NEXT: } byte_size(4)
[all …]
|
| /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 …]
|
| H A D | 2.Process.rst | 38 deemed to be sufficiently stable (and which is accepted by the development
70 considered to be sufficiently stable and the final release is made.
77 September 15 5.3 stable release
86 November 24 5.4 stable release
90 the stable release? The most significant metric used is the list of
97 The developers' goal is to fix all known regressions before the stable
106 Once a stable release is made, its ongoing maintenance is passed off to the
107 "stable team," currently Greg Kroah-Hartman. The stable team will release
108 occasional updates to the stable release using the 5.x.y numbering scheme.
111 kernel. Kernels will typically receive stable updates for a little more
[all …]
|
| H A D | howto.rst | 127 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
129 not have a stable API within the kernel, including things like:
152 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
153 This file describes the rules on how the stable kernel releases
238 - Various stable trees with multiple major numbers
278 Various stable trees with multiple major numbers
281 Kernels with 3-part versions are -stable kernels. They contain
284 in a major stable series increments the third part of the version
287 This is the recommended branch for users who want the most recent stable
291 Stable trees are maintained by the "stable" team <stable@vger.kernel.org>, and
[all …]
|
| H A D | handling-regressions.rst | 116 Documentation/process/stable-kernel-rules.rst already explain in more detail:
130 the fix for backporting using the ``Cc: stable@vger.kernel.org`` tag.
166 mainline, stable, or longterm release (either directly or via backport).
179 particular hardware environment, distribution, or stable/longterm series.
182 into a recent mainline, stable, or longterm release (either directly or via
209 subsystem maintainer might be unavailable. Also CC the stable team, when you
210 know such a regression made it into a mainline, stable, or longterm release.
224 Regarding stable and longterm kernels:
226 * You are free to leave regressions to the stable team, if they at no point in
230 twelve months, ensure to tag the fix with "Cc: stable@vger.kernel.org", as a
[all …]
|
| /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":
40 Procedura per sottomettere patch per i sorgenti -stable
45 di revisione -stable, ma dovrebbe seguire le procedure descritte in
48 Ci sono tre opzioni per inviare una modifica per i sorgenti -stable:
50 1. Aggiungi un'etichetta 'stable' alla descrizione della patch al momento della
52 2. Chiedere alla squadra "stable" di prendere una patch già applicata sui
54 3. Sottomettere una patch alla squadra "stable" equivalente ad una modifica già
83 Cc: stable@vger.kernel.org
[all …]
|
| /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 …]
|
| /linux/fs/bcachefs/ |
| H A D | sb-counters.c | 42 unsigned stable = counters_to_stable_map[i]; in bch2_sb_counters_to_text() local
43 if (stable < nr) in bch2_sb_counters_to_text()
46 le64_to_cpu(ctrs->d[stable])); in bch2_sb_counters_to_text()
59 unsigned stable = counters_to_stable_map[i]; in bch2_sb_counters_to_cpu() local
60 if (stable < nr) { in bch2_sb_counters_to_cpu()
61 u64 v = le64_to_cpu(ctrs->d[stable]); in bch2_sb_counters_to_cpu()
86 unsigned stable = counters_to_stable_map[i]; in bch2_sb_counters_from_cpu() local
87 if (stable < nr) in bch2_sb_counters_from_cpu()
88 ctrs->d[stable] = cpu_to_le64(percpu_u64_get(&c->counters[i])); in bch2_sb_counters_from_cpu()
132 unsigned stable = counters_to_stable_map[i]; in bch2_ioctl_query_counters() local
[all …]
|
| /linux/tools/testing/selftests/net/ |
| H A D | gre_ipv6_lladdr.sh | 62 # device (eui64, none, stable-privacy or random).
89 "stable-privacy")
91 MATCH_REGEXP="stable-privacy"
92 MSG="${GRE_TYPE}, mode: 2 (stable privacy), ${LOCAL_IP} -> ${REMOTE_IP}"
94 # Initialise stable_secret (required for stable-privacy mode)
99 MATCH_REGEXP="stable-privacy"
131 for MODE in "eui64" "none" "stable-privacy" "random"; do
147 for MODE in "eui64" "none" "stable-privacy" "random"; do
|
| /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 …]
|
| /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.
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 11 Are you facing a regression with vanilla kernels from the same stable or
13 <https://lore.kernel.org/lkml/>`_ and the `Linux stable mailing list
14 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
17 mailing list (stable@vger.kernel.org) and CC the regressions list
30 supported stable or longterm series as well? Then install its latest release.
101 * If you are facing a regression within a stable or longterm version line
103 'Dealing with regressions within a stable and longterm kernel line'.
118 the latest 'stable' Linux can be an acceptable alternative in some
130 stable and longterm kernels.
[all …]
|
| H A D | verify-bugs-and-bisect-regressions.rst | 62 git remote add -t master stable \
63 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
141 git remote set-branches --add stable linux-6.1.y
142 git fetch stable
261 even if you face a problem with a kernel from a 'stable/longterm' series
322 * Something regressed when updating from a stable/longterm release
324 stable/longterm version based on one (say 6.1.5)? Then consider the
331 a later one (like 6.1-rc1) or a stable/longterm release based on it
335 * Something regressed when updating within a stable/longterm series (say
384 preparing things to add branches for stable/longterm series later::
[all …]
|
| /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
|
| /linux/include/uapi/linux/ |
| H A D | nfs_fs.h | 34 #define FLUSH_STABLE 4 /* commit to stable storage */
37 #define FLUSH_COND_STABLE 32 /* conditional stable write - only stable
|
| /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
|
| /linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 7 patches for stable kernels.
393 Stable submission
396 Q: I need a specific BPF commit in stable kernels. What should I do?
398 A: In case you need a specific fix in stable kernels, first check whether
401 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/
412 Q: Do you also backport to kernels not currently maintained as stable?
415 maintained by the stable maintainers, then you are on your own.
417 The current stable and longterm stable kernels are all listed here:
421 Q: The BPF patch I am about to submit needs to go to stable as well
428 Never add "``Cc: stable@vger.kernel.org``" to the patch description, but
[all …]
|
| /linux/scripts/gendwarfksyms/ |
| H A D | gendwarfksyms.c | 29 int stable; variable
43 " -s, --stable Support kABI stability features\n" in usage()
104 { "stable", 0, NULL, 's' }, in main()
118 stable = 1; in main()
|
| /linux/kernel/sched/ |
| H A D | clock.c | 41 * Otherwise it tries to create a semi stable clock from a mixture of other
73 * We must start with !__sched_clock_stable because the unstable -> stable
74 * transition is accurate, while the stable -> unstable transition is not.
77 * will become stable, such that there's only a single 1 -> 0 transition.
128 * Attempt to make the (initial) unstable->stable transition continuous. in __set_sched_clock_stable()
133 printk(KERN_INFO "sched_clock: Marking stable (%lld, %lld)->(%lld, %lld)\n", in __set_sched_clock_stable()
437 * The watchdog just found this TSC to (still) be stable, so now is a in sched_clock_tick_stable()
|
| /linux/rust/kernel/ |
| H A D | lib.rs | 19 // Stable since Rust 1.79.0.
22 // Stable since Rust 1.81.0.
25 // Stable since Rust 1.82.0.
28 // Stable since Rust 1.83.0.
34 // Expected to become stable.
37 // `feature(derive_coerce_pointee)` is expected to become stable. Before Rust
|
| /linux/Documentation/mm/damon/ |
| H A D | maintainer-profile.rst | 23 in `mm-stable <https://git.kernel.org/akpm/mm/h/mm-stable>`_, and finally
57 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ and `mm-stable
58 <https://git.kernel.org/akpm/mm/h/mm-stable>`_ trees depend on the memory
|
| /linux/include/linux/ |
| H A D | smp.h | 244 * smp_processor_id() - get the current (stable) CPU id
249 * The CPU id is stable when:
256 * when smp_processor_id() is used when the CPU id is not stable.
260 * Allow the architecture to differentiate between a stable and unstable read.
262 * regular asm read for the stable.
|
| /linux/Documentation/kbuild/ |
| H A D | gendwarfksyms.rst | 31 -s, --stable Support kABI stability features
88 Maintaining a stable kABI
97 features are all gated behind the **--stable** command line flag and are
98 not used in the mainline kernel. To use stable features during a kernel
274 in the published ABI, keeping symbol versions stable using the more
306 a stable symbol versions cannot be reasonably achieved using other
394 With **--stable**, both versions produce the same symbol version. The
|