Searched full:stable (Results 1 – 25 of 674) sorted by relevance
12345678910>>...27
| /linux-5.10/Documentation/process/ |
| D | stable-kernel-rules.rst | 3 Everything you ever wanted to know about Linux -stable releases
7 "-stable" tree:
35 Procedure for submitting patches to the -stable tree
38 - If the patch covers files in net/ or drivers/net please follow netdev stable
41 after first checking the stable networking queue at
42 https://patchwork.kernel.org/bundle/netdev/stable/?state=*
44 - Security patches should not be handled (solely) by the -stable review
56 To have the patch automatically included in the stable tree, add the tag
60 Cc: stable@vger.kernel.org
63 the stable tree without anything else needing to be done by the author
[all …]
|
| 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
|
| D | applying-patches.rst | 248 The 5.x.y (-stable) and 5.x patches live at
257 The stable -rc patches live at
259 https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/
265 These are the base stable releases released by Linus. The highest numbered
268 If regressions or other serious flaws are found, then a -stable fix patch
300 Kernels with 3-digit versions are -stable kernels. They contain small(ish)
304 This is the recommended branch for users who want the most recent stable
309 the current stable kernel.
313 The -stable team usually do make incremental patches available as well
341 These kernels are not stable and you should expect occasional breakage if
[all …]
|
| 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 …]
|
| D | howto.rst | 128 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
130 not have a stable API within the kernel, including things like:
153 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
154 This file describes the rules on how the stable kernel releases
239 - Various stable trees with multiple major numbers
279 Various stable trees with multiple major numbers
282 Kernels with 3-part versions are -stable kernels. They contain
285 in a major stable series increments the third part of the version
288 This is the recommended branch for users who want the most recent stable
292 Stable trees are maintained by the "stable" team <stable@vger.kernel.org>, and
[all …]
|
| /linux-5.10/Documentation/translations/ja_JP/ |
| 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 …]
|
| D | howto.rst | 144 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
168 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
169 このファイルはどのように stable カーネルのリリースが行われるかのルー
258 - 4.x.y -stable カーネルツリー
298 4.x.y -stable カーネルツリー
301 バージョン番号が3つの数字に分かれているカーネルは -stable カーネルです。
311 4.x.y は "stable" チーム <stable@vger.kernel.org> でメンテされており、
317 Documentation/process/stable-kernel-rules.rst ファイルにはどのような種
318 類の変更が -stable ツリーに受け入れ可能か、またリリースプロセスがどう
|
| /linux-5.10/Documentation/translations/it_IT/process/ |
| 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
49 https://patchwork.kernel.org/bundle/netdev/stable/?state=*
51 di revisione -stable, ma dovrebbe seguire le procedure descritte in
68 Cc: stable@vger.kernel.org
80 stable@vger.kernel.org includendo: il titolo della patch, l'identificativo
90 precedenza, a stable@vger.kernel.org. Dovete annotare nel changelog
121 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
[all …]
|
| /linux-5.10/Documentation/networking/ |
| D | netdev-FAQ.rst | 147 Q: How can I tell what patches are queued up for backporting to the various stable releases?
149 A: Normally Greg Kroah-Hartman collects stable commits himself, but for
155 https://patchwork.kernel.org/bundle/netdev/stable/?state=*
160 https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
162 A quick way to find whether the patch is in this stable-queue is to
166 stable-queue$ git grep -l 284041ef21fdf2e
170 stable/stable-queue$
172 Q: I see a network patch and I think it should be backported to stable.
174 Q: Should I request it via stable@vger.kernel.org like the references in
175 the kernel's Documentation/process/stable-kernel-rules.rst file say?
[all …]
|
| /linux-5.10/Documentation/ABI/ |
| 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.
|
| /linux-5.10/drivers/parisc/ |
| 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-5.10/Documentation/vm/ |
| D | ksm.rst | 24 KSM maintains reverse mapping information for KSM pages in the stable
28 the node of the stable tree that represents such KSM page points to a
30 KSM page points to the stable tree node.
33 the stable tree. The tree node becomes a "chain" that links one or
42 This way the stable tree lookup computational complexity is unaffected
45 stable tree itself.
|
| /linux-5.10/mm/ |
| D | ksm.c | 64 * Therefore KSM uses two data structures - the stable and the unstable tree.
66 * The stable tree holds pointers to all the merged pages (ksm pages), sorted
69 * and therefore this tree is called the stable tree.
71 * The stable tree node includes information required for reverse
75 * KSM maintains two types of nodes in the stable tree:
86 * In addition to the stable tree, KSM uses a second data structure called the
104 * 4) KSM never flushes the stable tree, which means that even if it were to
106 * it is secured in the stable tree. (When we scan a new page, we first
107 * compare it against the stable tree, and then against the unstable tree.)
110 * stable trees and multiple unstable trees: one of each for each NUMA node.
[all …]
|
| /linux-5.10/Documentation/admin-guide/ |
| D | abi-stable.rst | 1 ABI stable symbols
4 Documents the interfaces that the developer has defined to be stable.
13 .. kernel-abi:: $srctree/Documentation/ABI/stable
|
| D | abi-testing.rst | 4 Documents interfaces that are felt to be stable,
13 be marked stable.
|
| /linux-5.10/Documentation/input/devices/ |
| 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-5.10/include/uapi/linux/ |
| 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-5.10/Documentation/devicetree/bindings/ |
| 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-5.10/include/linux/ |
| D | smp.h | 208 * smp_processor_id() - get the current (stable) CPU id
213 * The CPU id is stable when:
220 * when smp_processor_id() is used when the CPU id is not stable.
224 * Allow the architecture to differentiate between a stable and unstable read.
226 * regular asm read for the stable.
|
| /linux-5.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 7 patches for stable kernels.
354 Stable submission
357 Q: I need a specific BPF commit in stable kernels. What should I do?
359 A: In case you need a specific fix in stable kernels, first check whether
362 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/
372 Q: Do you also backport to kernels not currently maintained as stable?
375 maintained by the stable maintainers, then you are on your own.
377 The current stable and longterm stable kernels are all listed here:
381 Q: The BPF patch I am about to submit needs to go to stable as well
388 Never add "``Cc: stable@vger.kernel.org``" to the patch description, but
[all …]
|
| /linux-5.10/include/media/ |
| D | h264-ctrls.h | 6 * It turns out that these structs are not stable yet and will undergo
7 * more changes. So keep them private until they are stable and ready to
24 /* Our pixel format isn't stable at the moment */
30 * stable. It should be fixed eventually.
|
| D | hevc-ctrls.h | 6 * It turns out that these structs are not stable yet and will undergo
7 * more changes. So keep them private until they are stable and ready to
16 /* The pixel format isn't stable at the moment and will likely be renamed. */
54 /* The controls are not stable at the moment and will likely be reworked. */
|
| D | fwht-ctrls.h | 6 * It turns out that these structs are not stable yet and will undergo
7 * more changes. So keep them private until they are stable and ready to
|
| /linux-5.10/kernel/sched/ |
| D | clock.c | 41 * Otherwise it tries to create a semi stable clock from a mixture of other
75 * We must start with !__sched_clock_stable because the unstable -> stable
76 * transition is accurate, while the stable -> unstable transition is not.
79 * will become stable, such that there's only a single 1 -> 0 transition.
130 * Attempt to make the (initial) unstable->stable transition continuous. in __set_sched_clock_stable()
135 printk(KERN_INFO "sched_clock: Marking stable (%lld, %lld)->(%lld, %lld)\n", in __set_sched_clock_stable()
414 * The watchdog just found this TSC to (still) be stable, so now is a in sched_clock_tick_stable()
|
| /linux-5.10/include/sound/ |
| D | cs4271.h | 16 * The CS4271 requires its LRCLK and MCLK to be stable before its RESET
25 * Note that this is not needed in case the clocks are stable
|
12345678910>>...27