| /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 | 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 | maintainer-kvm-x86.rst | 68 especially for the current release and or stable trees, get to jump the queue.
101 arch patch/series should instead be based on a common, stable point in KVM's
140 and APM are constantly changing, and so the numbers/labels aren't stable.
229 need to be backported to stable kernels, and even if the change fixes a bug in
233 "Cc: stable@vger.kernel" (though the email itself doesn't need to Cc: stable);
378 SHA1s are not 100% guaranteed to be stable until they land in Linus' tree! A
379 SHA1 is *usually* stable once a notification has been sent, but things happen.
|
| /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/tools/testing/selftests/net/ |
| H A D | gre_ipv6_lladdr.sh | 69 # device (eui64, none, stable-privacy or random).
96 "stable-privacy")
98 MATCH_REGEXP="stable-privacy"
99 MSG="${GRE_TYPE}, mode: 2 (stable privacy), ${LOCAL_IP} -> ${REMOTE_IP}"
101 # Initialise stable_secret (required for stable-privacy mode)
106 MATCH_REGEXP="stable-privacy"
138 for MODE in "eui64" "none" "stable-privacy" "random"; do
154 for MODE in "eui64" "none" "stable-privacy" "random"; do
|
| H A D | ipv6_fragmentation.c | 5 * Kernel selftest for the IPv6 fragmentation regression which affected stable
8 * https://lore.kernel.org/stable/aElivdUXqd1OqgMY@karahi.gladserv.com
10 * Commit: a18dfa9925b9 ("ipv6: save dontfrag in cork") was backported to stable
|
| /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/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/tools/testing/selftests/drivers/net/lib/py/ |
| H A D | load.py | 60 middle part of the run where throughput is typically stable.
77 stable = samples[3:-3]
79 avg = sum(stable) / len(stable)
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfsd-maintainer-entry-profile.rst | 235 The NFSD maintainers prefer to add stable tagging themselves, after
237 may suggest stable tagging, but be aware that many version
238 management tools add such stable Cc's when you post your patches.
239 Don't add "Cc: stable" unless you are absolutely sure the patch
240 needs to go to stable during the initial submission process.
386 Please be aware that many version management tools add the stable
389 Don't add "Cc: stable" unless you are absolutely sure the patch
390 needs to go to stable@ during the initial submission process.
444 Stable and LTS support
539 the Fixes: and Cc: stable annotations on patches, and seeing that
|
| /linux/Documentation/kbuild/ |
| H A D | gendwarfksyms.rst | 54 -s, --stable Support kABI stability features
111 Maintaining a stable kABI
120 features are all gated behind the **--stable** command line flag and are
121 not used in the mainline kernel. To use stable features during a kernel
297 in the published ABI, keeping symbol versions stable using the more
329 a stable symbol versions cannot be reasonably achieved using other
417 With **--stable**, both versions produce the same symbol version. The
|
| /linux/include/linux/ |
| H A D | fsnotify.h | 315 * Caller must make sure that dentry->d_name is stable.
329 * Caller must make sure that new_dentry->d_name is stable.
346 * Caller must make sure that dentry->d_name is stable.
383 * Caller must make sure that dentry->d_name is stable.
396 * Caller must make sure that dentry->d_name is stable.
410 * Caller must make sure that dentry->d_name is stable.
|
| /linux/include/sound/ |
| H A D | cs4271.h | 15 * The CS4271 requires its LRCLK and MCLK to be stable before its RESET
24 * Note that this is not needed in case the clocks are stable
|
| /linux/Documentation/translations/ko_KR/process/ |
| H A D | howto.rst | 148 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
173 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
295 세개의 버젼 넘버로 이루어진 버젼의 커널들은 -stable 커널들이다. 그것들은 해당
297 중요한 수정들을 포함한다. 주요 stable 시리즈 릴리즈는 세번째 버젼 넘버를
303 -stable 트리들은 "stable" 팀<stable@vger.kernel.org>에 의해 관리되며 거의 매번
306 커널 트리 문서들 내의 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
307 파일은 어떤 종류의 변경들이 -stable 트리로 들어왔는지와
|
| /linux/net/ceph/crush/ |
| H A D | mapper.c | 447 * @stable: stable mode starts rep=0 in the recursive call for all replicas
466 unsigned int stable, in crush_choose_firstn() argument
482 …p %d tries %d recurse_tries %d local_retries %d local_fallback_retries %d parent_r %d stable %d\n", in crush_choose_firstn()
486 parent_r, stable); in crush_choose_firstn()
488 for (rep = stable ? 0 : outpos; rep < numrep && count > 0 ; rep++) { in crush_choose_firstn()
570 x, stable ? 1 : outpos+1, 0, in crush_choose_firstn()
577 stable, in crush_choose_firstn()
644 * crush_choose_indep: alternative breadth-first positionally stable mapping
931 int stable = map->chooseleaf_stable; in crush_do_rule() local
986 stable = curstep->arg1; in crush_do_rule()
[all …]
|
| /linux/Documentation/translations/zh_TW/process/ |
| H A D | index.rst | 48 stable-api-nonsense
49 stable-kernel-rules
|