Searched full:stable (Results 1 – 25 of 890) sorted by relevance
12345678910>>...36
7 * Examples for kABI stability features with --stable.21 * ./gendwarfksyms --stable --dump-dies \23 * FileCheck examples/kabi_ex.h --check-prefix=STABLE42 * STABLE: variable structure_type s {43 * STABLE-NEXT: }58 * STABLE: variable enumeration_type e {59 * STABLE-NEXT: enumerator A = 0 ,60 * STABLE-NEXT: enumerator D = 12345678961 * STABLE-NEXT: } byte_size(4)74 * STABLE: variable structure_type ex0a {[all …]
3 Everything you ever wanted to know about Linux -stable releases7 "-stable" tree:34 Procedure for submitting patches to the -stable tree39 Security patches should not be handled (solely) by the -stable review43 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 for47 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 already60 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 …]
11 kernel interface, nor does it have a stable kernel interface**.19 the syscall interface. That interface is **very** stable over time, and23 on being stable.28 You think you want a stable kernel interface, but you really do not, and29 you don't even know it. What you want is a stable running driver, and32 tree, all of which has made Linux into such a strong, stable, and mature53 So, there are two main topics here, binary kernel interfaces and stable60 Assuming that we had a stable kernel source interface for the kernel, a101 Stable Kernel Source Interfaces140 stable source interface, a new interface would have been created, and
248 The 5.x.y (-stable) and 5.x patches live at261 The stable -rc patches live at263 https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/269 These are the base stable releases released by Linus. The highest numbered272 If regressions or other serious flaws are found, then a -stable fix patch304 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 stable313 the current stable kernel.315 The -stable team provides normal as well as incremental patches. Below is341 of base 5.x kernel, they are applied on top of previous stable kernel[all …]
38 deemed to be sufficiently stable (and which is accepted by the development70 considered to be sufficiently stable and the final release is made.77 September 15 5.3 stable release86 November 24 5.4 stable release90 the stable release? The most significant metric used is the list of97 The developers' goal is to fix all known regressions before the stable106 Once a stable release is made, its ongoing maintenance is passed off to the107 "stable team," currently Greg Kroah-Hartman. The stable team will release108 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 …]
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 releases238 - Various stable trees with multiple major numbers278 Various stable trees with multiple major numbers281 Kernels with 3-part versions are -stable kernels. They contain284 in a major stable series increments the third part of the version287 This is the recommended branch for users who want the most recent stable291 Stable trees are maintained by the "stable" team <stable@vger.kernel.org>, and[all …]
3 :Original: :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`8 Tutto quello che volevate sapere sui rilasci -stable di Linux12 "-stable":40 Procedura per sottomettere patch per i sorgenti -stable45 di revisione -stable, ma dovrebbe seguire le procedure descritte in48 Ci sono tre opzioni per inviare una modifica per i sorgenti -stable:50 1. Aggiungi un'etichetta 'stable' alla descrizione della patch al momento della52 2. Chiedere alla squadra "stable" di prendere una patch già applicata sui54 3. Sottomettere una patch alla squadra "stable" equivalente ad una modifica già83 Cc: stable@vger.kernel.org[all …]
2 This is Japanese translated version of "Documentation/process/stable-kernel-rules.rst".15 linux-2.6.29/Documentation/process/stable-kernel-rules.rst28 ずっと知りたかった 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 …]
42 unsigned stable = counters_to_stable_map[i]; in bch2_sb_counters_to_text() local43 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() local60 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() local87 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 …]
13 stable/15 defined to be stable. Userspace programs are free to use these22 This directory documents interfaces that are felt to be stable,29 be marked stable. Programs that use these interfaces are72 Interfaces in stable may move to obsolete, as long as the proper78 Interfaces in the testing state can move to the stable state when the87 stable:96 itself. See Documentation/process/stable-api-nonsense.rst.
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"; do147 for MODE in "eui64" "none" "stable-privacy" "random"; do
3 * Interfaces to retrieve and set PDC Stable options (firmware)8 * "A minimum of 96 bytes of Stable Storage is required. Providing more than9 * 96 bytes of Stable Storage is optional [...]. Failure to provide the15 * following code can deal with just 96 bytes of Stable Storage, and all62 #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 time132 * content of the stable storage WRT various paths in these structs. We read[all …]
22 KSM maintains reverse mapping information for KSM pages in the stable26 the node of the stable tree that represents such KSM page points to a28 KSM page points to the stable tree node.31 the stable tree. The tree node becomes a "chain" that links one or40 This way the stable tree lookup computational complexity is unaffected43 stable tree itself.
72 * Therefore KSM uses two data structures - the stable and the unstable tree.74 * The stable tree holds pointers to all the merged pages (ksm pages), sorted77 * and therefore this tree is called the stable tree.79 * The stable tree node includes information required for reverse83 * KSM maintains two types of nodes in the stable tree:94 * In addition to the stable tree, KSM uses a second data structure called the112 * 4) KSM never flushes the stable tree, which means that even if it were to114 * it is secured in the stable tree. (When we scan a new page, we first115 * compare it against the stable tree, and then against the unstable tree.)118 * stable trees and multiple unstable trees: one of each for each NUMA node.[all …]
3 ABI stable symbols6 Documents the interfaces that the developer has defined to be stable.15 .. kernel-abi:: stable
11 Are you facing a regression with vanilla kernels from the same stable or13 <https://lore.kernel.org/lkml/>`_ and the `Linux stable mailing list14 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable17 mailing list (stable@vger.kernel.org) and CC the regressions list30 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 line103 'Dealing with regressions within a stable and longterm kernel line'.118 the latest 'stable' Linux can be an acceptable alternative in some130 stable and longterm kernels.[all …]
62 git remote add -t master stable \63 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git141 git remote set-branches --add stable linux-6.1.y142 git fetch stable261 even if you face a problem with a kernel from a 'stable/longterm' series322 * Something regressed when updating from a stable/longterm release324 stable/longterm version based on one (say 6.1.5)? Then consider the331 a later one (like 6.1-rc1) or a stable/longterm release based on it335 * Something regressed when updating within a stable/longterm series (say384 preparing things to add branches for stable/longterm series later::[all …]
3 Stable ABI Files6 .. kernel-abi:: stable
15 Some encoders have both outputs low in stable states, others also have16 a stable state with both outputs high (half-period mode) and some have17 a stable state in all steps (quarter-period mode).50 rotational direction based on the last stable state. Events are reported in51 states b) and d) given that the new stable state is different from the last
141 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`165 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`166 このファイルはどのように stable カーネルのリリースが行われるかのルー293 バージョン番号が3つの数字に分かれているカーネルは -stable カーネルです。304 安定版ツリーは"stable" チーム <stable@vger.kernel.org> でメンテされており、310 Documentation/process/stable-kernel-rules.rst ファイルにはどのような種311 類の変更が -stable ツリーに受け入れ可能か、またリリースプロセスがどう
34 #define FLUSH_STABLE 4 /* commit to stable storage */37 #define FLUSH_COND_STABLE 32 /* conditional stable write - only stable
7 I. Regarding stable bindings/ABI, we quote from the 2013 ARM mini-summit10 "That still leaves the question of, what does a stable binding look11 like? Certainly a stable binding means that a newer kernel will not
7 patches for stable kernels.393 Stable submission396 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 whether401 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 well428 Never add "``Cc: stable@vger.kernel.org``" to the patch description, but[all …]
29 int stable; variable43 " -s, --stable Support kABI stability features\n" in usage()104 { "stable", 0, NULL, 's' }, in main()118 stable = 1; in main()
23 in `mm-stable <https://git.kernel.org/akpm/mm/h/mm-stable>`_, and finally57 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ and `mm-stable58 <https://git.kernel.org/akpm/mm/h/mm-stable>`_ trees depend on the memory