Searched full:stable (Results 1 – 25 of 1261) sorted by relevance
12345678910>>...51
| /kernel/linux/linux-4.19/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.ozlabs.org/bundle/davem/stable/?series=&submitter=&state=*&q=&archive=
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 | 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 2.6.x release is made.
77 January 28 4.15 stable release
85 April 1 4.17 stable release
89 the stable release? The most significant metric used is the list of
96 The developers' goal is to fix all known regressions before the stable
105 Once a stable release is made, its ongoing maintenance is passed off to the
106 "stable team," currently consisting of Greg Kroah-Hartman. The stable team
107 will release occasional updates to the stable release using the 4.x.y
110 next development kernel. Kernels will typically receive stable updates for
[all …]
|
| /kernel/linux/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 ツリーに受け入れ可能か、またリリースプロセスがどう
|
| /kernel/linux/linux-4.19/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 カーネルツリー
299 4.x.y -stable カーネルツリー
302 バージョン番号が3つの数字に分かれているカーネルは -stable カーネルです。
312 4.x.y は "stable" チーム <stable@vger.kernel.org> でメンテされており、
318 Documentation/process/stable-kernel-rules.rst ファイルにはどのような種
319 類の変更が -stable ツリーに受け入れ可能か、またリリースプロセスがどう
|
| /kernel/linux/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 - Security patches should not be handled (solely) by the -stable review
50 To have the patch automatically included in the stable tree, add the tag
54 Cc: stable@vger.kernel.org
57 the stable tree without anything else needing to be done by the author
66 stable@vger.kernel.org containing the subject of the patch, the commit ID,
76 stable@vger.kernel.org. You must note the upstream commit ID in the
104 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
[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 …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | netdev-FAQ.rst | 134 Q: How can I tell what patches are queued up for backporting to the various stable releases?
136 A: Normally Greg Kroah-Hartman collects stable commits himself, but for
142 http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
147 https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
149 A quick way to find whether the patch is in this stable-queue is to
153 stable-queue$ git grep -l 284041ef21fdf2e
157 stable/stable-queue$
159 Q: I see a network patch and I think it should be backported to stable.
161 Q: Should I request it via stable@vger.kernel.org like the references in
162 the kernel's Documentation/process/stable-kernel-rules.rst file say?
[all …]
|
| /kernel/linux/linux-4.19/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
63 Interfaces in stable may move to obsolete, as long as the proper
69 Interfaces in the testing state can move to the stable state when the
78 stable:
87 itself. See Documentation/process/stable-api-nonsense.rst.
|
| /kernel/linux/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.
|
| /kernel/linux/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 …]
|
| /kernel/linux/linux-4.19/drivers/parisc/ |
| D | pdc_stable.c | 2 * Interfaces to retrieve and set PDC Stable options (firmware)
21 * "A minimum of 96 bytes of Stable Storage is required. Providing more than
22 * 96 bytes of Stable Storage is optional [...]. Failure to provide the
28 * following code can deal with just 96 bytes of Stable Storage, and all
75 #define PDCS_PREFIX "PDC Stable Storage"
88 MODULE_DESCRIPTION("sysfs interface to HP PDC Stable Storage data");
92 /* holds Stable Storage size. Initialized once and for all, no lock needed */
102 unsigned long addr; /* entry address in stable storage */
143 * The general idea is that you don't read from the Stable Storage every time
145 * content of the stable storage WRT various paths in these structs. We read
[all …]
|
| /kernel/linux/linux-4.19/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-4.19/mm/ |
| D | ksm.c | 65 * Therefore KSM uses two data structures - the stable and the unstable tree.
67 * The stable tree holds pointers to all the merged pages (ksm pages), sorted
70 * and therefore this tree is called the stable tree.
72 * The stable tree node includes information required for reverse
76 * KSM maintains two types of nodes in the stable tree:
87 * In addition to the stable tree, KSM uses a second data structure called the
105 * 4) KSM never flushes the stable tree, which means that even if it were to
107 * it is secured in the stable tree. (When we scan a new page, we first
108 * compare it against the stable tree, and then against the unstable tree.)
111 * stable trees and multiple unstable trees: one of each for each NUMA node.
[all …]
|
| /kernel/linux/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 …]
|
| /kernel/linux/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
|
| /kernel/linux/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/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
|
12345678910>>...51