Searched refs:stable (Results 1 – 25 of 91) sorted by relevance
1234
| /linux-2.6.39/Documentation/ja_JP/ |
| D | stable_kernel_rules.txt | 28 ずっと知りたかった Linux 2.6 -stable リリースの全て
30 "-stable" ツリーにどのような種類のパッチが受け入れられるか、どのような
48 Linus のツリーでのコミットID を -stable へのパッチ投稿の際に引用す
51 -stable ツリーにパッチを送付する手続き-
53 - 上記の規則に従っているかを確認した後に、stable@kernel.org にパッチ
59 メンテナーによるレビューのために -stable キューに追加される。
60 - パッチに stable@kernel.org のアドレスが付加されているときには、それ
61 が Linus のツリーに入る時に自動的に stable チームに email される。
62 - セキュリティパッチはこのエイリアス (stable@kernel.org) に送られるべ
67 - -stable メンテナがレビューサイクルを決めるとき、パッチはレビュー委
[all …]
|
| D | HOWTO | 180 このファイルはどのように stable カーネルのリリースが行われるかのルー
257 - 2.6.x.y -stable カーネルツリー
305 2.6.x.y -stable カーネルツリー
308 バージョン番号が4つの数字に分かれているカーネルは -stable カーネルです。
318 2.6.x.y は "stable" チーム <stable@kernel.org> でメンテされており、必
324 イルにはどのような種類の変更が -stable ツリーに受け入れ可能か、またリ
|
| /linux-2.6.39/Documentation/ |
| D | stable_kernel_rules.txt | 1 Everything you ever wanted to know about Linux 2.6 -stable releases.
4 "-stable" tree:
24 Procedure for submitting patches to the -stable tree:
27 stable@kernel.org. You must note the upstream commit ID in the changelog
29 - To have the patch automatically included in the stable tree, add the tag
30 Cc: stable@kernel.org
32 the stable tree without anything else needing to be done by the author
38 Cc: <stable@kernel.org> # .32.x: a1f84a3: sched: Check for idle
39 Cc: <stable@kernel.org> # .32.x: 1b9508f: sched: Rate-limit newidle
40 Cc: <stable@kernel.org> # .32.x: fd21073: sched: Fix affinity logic
[all …]
|
| D | stable_api_nonsense.txt | 7 kernel interface, nor does it have a stable kernel interface. Please
11 interface is _very_ stable over time, and will not break. I have old
14 that users and application programmers can count on being stable.
19 You think you want a stable kernel interface, but you really do not, and
20 you don't even know it. What you want is a stable running driver, and
23 tree, all of which has made Linux into such a strong, stable, and mature
44 So, there are two main topics here, binary kernel interfaces and stable
51 Assuming that we had a stable kernel source interface for the kernel, a
126 stable source interface, a new interface would have been created, and
|
| D | applying-patches.txt | 219 The 2.6.x.y (-stable) and 2.6.x patches live at
240 These are the base stable releases released by Linus. The highest numbered
243 If regressions or other serious flaws are found, then a -stable fix patch
272 Kernels with 4-digit versions are -stable kernels. They contain small(ish)
276 This is the recommended branch for users who want the most recent stable
281 the current stable kernel.
283 note: the -stable team usually do make incremental patches available as well
310 These kernels are not stable and you should expect occasional breakage if
311 you intend to run them. This is however the most stable of the main
313 stable kernel, so it is important that it be tested by as many people as
[all …]
|
| D | sysfs-rules.txt | 5 by the kernel developers that the Linux kernel does not provide a stable
7 may not be stable across kernel releases.
26 current kernel development. The goal of providing a stable interface
85 that should not be assumed to be stable across kernel releases.
|
| D | HOWTO | 121 not have a stable API within the kernel, including things like:
143 This file describes the rules on how the stable kernel releases
222 - 2.6.x.y -stable kernel tree
265 2.6.x.y -stable kernel tree
267 Kernels with 4-part versions are -stable kernels. They contain
271 This is the recommended branch for users who want the most recent stable
276 kernel is the current stable kernel.
278 2.6.x.y are maintained by the "stable" team <stable@kernel.org>, and are
285 documents what kinds of changes are acceptable for the -stable tree, and
353 more stable, you'll learn to fix real world problems and you will improve
|
| D | rfkill.txt | 120 For further details consult Documentation/ABI/stable/dev-rfkill and
121 Documentation/ABI/stable/sysfs-class-rfkill.
|
| D | debugging-via-ohci1394.txt | 77 yet stable) with kgdb over an memory-based communication module (kgdbom).
111 stable connection and has matching connectors (there are small 4-pin and
|
| /linux-2.6.39/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
66 Interfaces in stable may move to obsolete, as long as the proper
72 Interfaces in the testing state can move to the stable state when the
|
| /linux-2.6.39/Documentation/zh_CN/ |
| D | HOWTO | 196 - 2.6.x.y -stable内核源码树
229 2.6.x.y -stable（稳定版）内核源码树
231 由4个数字组成的内核版本号说明此内核是-stable版本。它们包含基于2.6.x版本
240 2.6.x.y版本由“稳定版”小组（邮件地址<stable@kernel.org>）维护，一般隔周发
|
| D | stable_kernel_rules.txt | 45 - 在确认了补丁符合以上的规则后，将补丁发送到stable@kernel.org。
|
| /linux-2.6.39/Documentation/ko_KR/ |
| D | HOWTO | 268 4 자리 숫자로 이루어진 버젼의 커널들은 -stable 커널들이다. 그것들은 2.6.x
278 2.6.x.y는 "stable" 팀<stable@kernel.org>에 의해 관리되며 거의 매번 격주로
282 종류의 변경들이 -stable 트리로 들어왔는지와 배포 프로세스가 어떻게
|
| D | stable_api_nonsense.txt | 28 않는(stable) 커널 인터페이스를 갖지 않는지를 설명하기 위해 쓰여졌다.
|
| /linux-2.6.39/Documentation/ABI/obsolete/ |
| D | o2cb | 9 See Documentation/ABI/stable/o2cb for more information on usage.
|
| /linux-2.6.39/Documentation/development-process/ |
| D | 2.Process | 33 deemed to be sufficiently stable (and which is accepted by the development
65 considered to be sufficiently stable and the final 2.6.x release is made.
71 January 4 2.6.37 stable release
80 March 14 2.6.38 stable release
83 the stable release? The most significant metric used is the list of
90 The developers' goal is to fix all known regressions before the stable
99 Once a stable release is made, its ongoing maintenance is passed off to the
100 "stable team," currently consisting of Greg Kroah-Hartman. The stable team
101 will release occasional updates to the stable release using the 2.6.x.y
104 next development kernel. Kernels will typically receive stable updates for
[all …]
|
| D | 5.Posting | 64 point - a stable or -rc release - rather than branching off the mainline at
274 next stable update. If so, stable@kernel.org should get a copy of the
275 patch. Also add a "Cc: stable@kernel.org" to the tags within the patch
276 itself; that will cause the stable team to get a notification when your
|
| /linux-2.6.39/drivers/virtio/ |
| D | Kconfig | 21 Currently, the ABI is not considered stable so there is no guarantee
|
| /linux-2.6.39/Documentation/ABI/stable/ |
| D | sysfs-module | 19 considered stable, only the fact that they will be
|
| /linux-2.6.39/drivers/staging/easycap/ |
| D | Kconfig | 43 Once binding to ALSA interface will be stable this option will be
|
| /linux-2.6.39/drivers/staging/wlags49_h25/ |
| D | TODO | 16 - once the driver runs it is very stable, but I have the impression
|
| /linux-2.6.39/drivers/staging/wlags49_h2/ |
| D | TODO | 16 - once the driver runs it is very stable, but I have the impression
|
| /linux-2.6.39/fs/nfs/ |
| D | write.c | 872 data->args.stable = NFS_UNSTABLE; in nfs_write_rpcsetup()
874 data->args.stable = NFS_DATA_SYNC; in nfs_write_rpcsetup()
876 data->args.stable = NFS_FILE_SYNC; in nfs_write_rpcsetup()
1210 if (resp->verf->committed < argp->stable && task->tk_status >= 0) { in nfs_writeback_done()
1226 resp->verf->committed, argp->stable); in nfs_writeback_done()
1250 argp->stable = NFS_FILE_SYNC; in nfs_writeback_done()
|
| /linux-2.6.39/Documentation/blockdev/ |
| D | nbd.txt | 15 Current state: It currently works. Network block device is stable.
|
| /linux-2.6.39/Documentation/sound/alsa/ |
| D | Bt87x.txt | 29 The driver is now stable. However, it doesn't know about many TV cards,
|
1234