| /Linux-v4.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 ツリーに受け入れ可能か、またリリースプロセスがどう
|
| D | stable_api_nonsense.txt | 2 This is a version of Documentation/process/stable-api-nonsense.rst into Japanese.
17 linux-2.6.22-rc4/Documentation/process/stable-api-nonsense.rst の和訳
|
| /Linux-v4.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 - Security patches should not be handled (solely) by the -stable review
53 To have the patch automatically included in the stable tree, add the tag
57 Cc: stable@vger.kernel.org
60 the stable tree without anything else needing to be done by the author
69 stable@vger.kernel.org containing the subject of the patch, the commit ID,
79 stable@vger.kernel.org. You must note the upstream commit ID in the
[all …]
|
| D | index.rst | 40 stable-api-nonsense
42 stable-kernel-rules
|
| 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
140 stable source interface, a new interface would have been created, and
|
| D | applying-patches.rst | 248 The 4.x.y (-stable) and 4.x patches live at
260 These are the base stable releases released by Linus. The highest numbered
263 If regressions or other serious flaws are found, then a -stable fix patch
295 Kernels with 3-digit versions are -stable kernels. They contain small(ish)
299 This is the recommended branch for users who want the most recent stable
304 the current stable kernel.
308 The -stable team usually do make incremental patches available as well
336 These kernels are not stable and you should expect occasional breakage if
337 you intend to run them. This is however the most stable of the main
339 stable kernel, so it is important that it be tested by as many people as
[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 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 …]
|
| /Linux-v4.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 …]
|
| /Linux-v4.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.
|
| /Linux-v4.19/Documentation/translations/ko_KR/ |
| D | howto.rst | 138 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
163 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
293 3 자리 숫자로 이루어진 버젼의 커널들은 -stable 커널들이다. 그것들은 4.x
303 4.x.y는 "stable" 팀<stable@vger.kernel.org>에 의해 관리되며 거의 매번 격주로
306 커널 트리 문서들 내에 Documentation/process/stable-kernel-rules.rst 파일은 어떤
307 종류의 변경들이 -stable 트리로 들어왔는지와 배포 프로세스가 어떻게
|
| D | stable_api_nonsense.txt | 2 This is a version of Documentation/process/stable-api-nonsense.rst translated
15 Documentation/process/stable-api-nonsense.rst
28 않는(stable) 커널 인터페이스를 갖지 않는지를 설명하기 위해 쓰여졌다.
|
| /Linux-v4.19/Documentation/translations/zh_CN/ |
| D | stable_kernel_rules.txt | 1 Chinese translated version of Documentation/process/stable-kernel-rules.rst
11 Documentation/process/stable-kernel-rules.rst 的中文翻译
45 - 在确认了补丁符合以上的规则后，将补丁发送到stable@vger.kernel.org。
|
| D | HOWTO | 119 Documentation/process/stable-api-nonsense.rst
137 Documentation/process/stable-kernel-rules.rst
194 - 2.6.x.y -stable内核源码树
225 2.6.x.y -stable（稳定版）内核源码树
227 由4个数字组成的内核版本号说明此内核是-stable版本。它们包含基于2.6.x版本
236 2.6.x.y版本由“稳定版”小组（邮件地址<stable@vger.kernel.org>）维护，一般隔周发
239 内核源码中的Documentation/process/stable-kernel-rules.rst文件具体描述了可被稳定
|
| D | stable_api_nonsense.txt | 1 Chinese translated version of Documentation/process/stable-api-nonsense.rst
12 Documentation/process/stable-api-nonsense.rst 的中文翻译
|
| /Linux-v4.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.
|
| /Linux-v4.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
|
| /Linux-v4.19/Documentation/devicetree/bindings/ |
| D | ABI.txt | 4 I. Regarding stable bindings/ABI, we quote from the 2013 ARM mini-summit
7 "That still leaves the question of, what does a stable binding look
8 like? Certainly a stable binding means that a newer kernel will not
|
| /Linux-v4.19/fs/nfs/ |
| D | nfstrace.h | 804 #define nfs_show_stable(stable) \ argument
805 __print_symbolic(stable, \
814 enum nfs3_stable_how stable
817 TP_ARGS(inode, offset, count, stable),
822 __field(enum nfs3_stable_how, stable)
833 __entry->stable = stable;
846 nfs_show_stable(__entry->stable)
863 __field(enum nfs3_stable_how, stable)
875 __entry->stable = writeverf->committed;
891 nfs_show_stable(__entry->stable),
|
| /Linux-v4.19/drivers/clk/ingenic/ |
| D | jz4740-cgu.c | 287 uint32_t clkgr, cppcr, stable; in jz4740_clock_resume() local
293 stable = BIT(jz4740_cgu_clocks[JZ4740_CLK_PLL].pll.stable_bit); in jz4740_clock_resume()
296 } while (!(cppcr & stable)); in jz4740_clock_resume()
|
| /Linux-v4.19/Documentation/devicetree/bindings/sound/ |
| D | cs4271.txt | 24 The CS4271 requires its LRCLK and MCLK to be stable before its RESET
33 Note that this is not needed in case the clocks are stable
|
| /Linux-v4.19/net/ceph/crush/ |
| D | mapper.c | 462 unsigned int stable, in crush_choose_firstn() argument
482 parent_r, stable); in crush_choose_firstn()
484 for (rep = stable ? 0 : outpos; rep < numrep && count > 0 ; rep++) { in crush_choose_firstn()
566 x, stable ? 1 : outpos+1, 0, in crush_choose_firstn()
573 stable, in crush_choose_firstn()
929 int stable = map->chooseleaf_stable; in crush_do_rule() local
984 stable = curstep->arg1; in crush_do_rule()
1045 stable, in crush_do_rule()
|
| /Linux-v4.19/Documentation/infiniband/ |
| D | sysfs.txt | 4 Documentation/ABI/stable/sysfs-class-infiniband.
|
| /Linux-v4.19/scripts/package/ |
| D | snapcraft.template | 5 grade: stable
|
| /Linux-v4.19/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 7 patches for stable kernels.
362 Q: I need a specific BPF commit in stable kernels. What should I do?
364 A: In case you need a specific fix in stable kernels, first check whether
367 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/
377 Q: Do you also backport to kernels not currently maintained as stable?
380 maintained by the stable maintainers, then you are on your own.
382 The current stable and longterm stable kernels are all listed here:
386 Q: The BPF patch I am about to submit needs to go to stable as well
393 Never add "``Cc: stable@vger.kernel.org``" to the patch description, but
399 Q: Queue stable patches
[all …]
|
