Home
last modified time | relevance | path

Searched refs:stable (Results 1 – 116 of 116) sorted by relevance

/linux-4.1.27/Documentation/ja_JP/
Dstable_kernel_rules.txt28 ずっと知りたかった 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 される。
62 - セキュリティパッチはこのエイリアス (stable@vger.kernel.org) に送られるべ
67 - -stable メンテナがレビューサイクルを決めるとき、パッチはレビュー委
[all …]
DHOWTO180 このファイルはどのように stable カーネルのリリースが行われるかのルー
257 - 3.x.y -stable カーネルツリー
305 3.x.y -stable カーネルツリー
308 バージョン番号が3つの数字に分かれているカーネルは -stable カーネルです。
318 3.x.y は "stable" チーム <stable@vger.kernel.org> でメンテされており、必
324 イルにはどのような種類の変更が -stable ツリーに受け入れ可能か、またリ
DSubmittingPatches369 ことは一般的で有用な慣習です。例えば、これは 2.6-stable ツリーでの一例です。
/linux-4.1.27/Documentation/
Dstable_kernel_rules.txt1 Everything you ever wanted to know about Linux -stable releases.
4 "-stable" tree:
30 Procedure for submitting patches to the -stable tree:
32 - If the patch covers files in net/ or drivers/net please follow netdev stable
35 - Security patches should not be handled (solely) by the -stable review
42 To have the patch automatically included in the stable tree, add the tag
43 Cc: stable@vger.kernel.org
45 the stable tree without anything else needing to be done by the author
51 stable@vger.kernel.org containing the subject of the patch, the commit ID,
58 stable@vger.kernel.org. You must note the upstream commit ID in the
[all …]
Dstable_api_nonsense.txt7 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
Dapplying-patches.txt219 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 …]
DHOWTO121 not have a stable API within the kernel, including things like:
143 This file describes the rules on how the stable kernel releases
222 - 4.x.y -stable kernel tree
265 4.x.y -stable kernel tree
267 Kernels with 3-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 4.x.y are maintained by the "stable" team <stable@vger.kernel.org>, and
285 documents what kinds of changes are acceptable for the -stable tree, and
352 more stable, you'll learn to fix real world problems and you will improve
Dsysfs-rules.txt5 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.
Ddebugging-via-ohci1394.txt75 yet stable) with kgdb over an memory-based communication module (kgdbom).
113 stable connection and has matching connectors (there are small 4-pin and
DSubmittingPatches119 installations run kernels from secondary stable trees or
298 toward the stable maintainers by putting a line like this:
300 Cc: stable@vger.kernel.org
305 conclusions on which patches should go to the stable trees. The networking
473 This practice is particularly helpful if you maintain a stable branch and
482 here's what we see in a 3.x-stable release:
593 review a bug fix. This tag also assists the stable kernel team in determining
594 which stable kernel versions should receive your fix. This is the preferred
Drfkill.txt123 For further details consult Documentation/ABI/stable/sysfs-class-rfkill.
DSubmittingDrivers115 often a good thing. If there is a stable working driver from
D00-INDEX423 - info on why the kernel does not have a stable in-kernel api or abi.
425 - rules and procedures for the -stable kernel releases.
Dintel_txt.txt81 This provides a more stable measurement and a higher assurance of
Dunshare.txt95 stable code to implement a new feature that may not get exercised
Doops-tracing.txt17 stable as humanly possible.
Dsvga.txt231 stable, explicit mode numbering allowed, "scan" implemented etc.
Dbcache.txt19 writes as completed until they're on stable storage).
Dpinctrl.txt202 stable value when nothing is driving the rail it is connected to, or when it's
Dkernel-parameters.txt650 stable over kernel options, but the vendor specific
/linux-4.1.27/Documentation/networking/
Dnetdev-FAQ.txt115 various stable releases?
117 A: Normally Greg Kroah-Hartman collects stable commits himself, but
122 http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
126 http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git
128 A quick way to find whether the patch is in this stable-queue is
131 stable-queue$ git grep -l 284041ef21fdf2e
135 stable/stable-queue$
137 Q: I see a network patch and I think it should be backported to stable.
138 Should I request it via "stable@vger.kernel.org" like the references in
141 A: No, not for networking. Check the stable queues as per above 1st to see
[all …]
Dpolicy-routing.txt97 Very clean, stable and robust algorithm for OSPF routing
DREADME.ipw2200410 1.0.0, 1.1.0, etc.) indicates a stable version that will be made
417 efforts to try and keep all snapshots reasonably stable, but due to the
Dcdc_mbim.txt339 - Documentation/ABI/stable/sysfs-bus-usb
Dip-sysctl.txt1225 privacy stable address generation if a DAD conflict is
1230 Controls the number of retries to generate a stable privacy
1566 be stable privacy ones by default. This can be changed via the
1572 of a system and keep it stable after that.
1574 By default the stable secret is unset.
Dixgb.txt191 stable configuration.
Darcnet-hardware.txt95 also work fine, because ARCnet is a very stable network. I personally use 75
Dbonding.txt186 stable or 0
/linux-4.1.27/Documentation/ABI/
DREADME12 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:
/linux-4.1.27/Documentation/devicetree/bindings/
DABI.txt4 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-4.1.27/Documentation/ko_KR/
DHOWTO268 3 자리 숫자로 이루어진 버젼의 커널들은 -stable 커널들이다. 그것들은 3.x
278 3.x.y는 "stable" 팀<stable@vger.kernel.org>에 의해 관리되며 거의 매번 격주로
282 종류의 변경들이 -stable 트리로 들어왔는지와 배포 프로세스가 어떻게
Dstable_api_nonsense.txt28 않는(stable) 커널 인터페이스를 갖지 않는지를 설명하기 위해 쓰여졌다.
/linux-4.1.27/Documentation/input/
Drotary-encoder.txt12 Some encoders have both outputs low in stable states, whereas others also have
13 a stable state with both outputs high (half-period mode).
43 rotational direction based on the last stable state. Events are reported in
44 states b) and d) given that the new stable state is different from the last
Djoystick-api.txt243 to be in the stable part of the API, and therefore may change without
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dcs4271.txt24 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-4.1.27/Documentation/zh_CN/
DHOWTO196 - 2.6.x.y -stable内核源码树
229 2.6.x.y -stable（稳定版）内核源码树
231 由4个数字组成的内核版本号说明此内核是-stable版本。它们包含基于2.6.x版本
240 2.6.x.y版本由“稳定版”小组（邮件地址<stable@vger.kernel.org>）维护，一般隔周发
Dstable_kernel_rules.txt45 - 在确认了补丁符合以上的规则后，将补丁发送到stable@vger.kernel.org。
/linux-4.1.27/Documentation/development-process/
D2.Process33 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 …]
D5.Posting64 point - a stable or -rc release - rather than branching off the mainline at
274 next stable update. If so, stable@vger.kernel.org should get a copy of
275 the patch. Also add a "Cc: stable@vger.kernel.org" to the tags within
276 the patch itself; that will cause the stable team to get a notification
D1.Intro145 - While kernel developers strive to maintain a stable interface to user
146 space, the internal kernel API is in constant flux. The lack of a stable
D6.Followthrough170 reports: the next mainline stable release, when prominent distributors pick
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dmatrix-keymap.txt2 defining the keys in the scope of linux key codes since that is a stable and
/linux-4.1.27/arch/xtensa/
DKconfig.debug35 Say 'N' on stable hardware.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-firmware-ofw17 in the future, but the symlink is the stable ABI.
Dsysfs-class-backlight-driver-adp887053 Documentation/ABI/stable/sysfs-class-backlight.
/linux-4.1.27/Documentation/hwmon/
Dda905514 different inputs. The track and hold circuit ensures stable input voltages at
Dda905214 different inputs. The track and hold circuit ensures stable input voltages at
/linux-4.1.27/Documentation/ABI/stable/
Dvdso22 ABI of those symbols is considered stable. It may vary across architectures,
Dsysfs-module23 considered stable, only the fact that they will be
/linux-4.1.27/Documentation/devicetree/bindings/video/
Dexynos_hdmi.txt24 parents i.e. sclk_pixel and sclk_hdmiphy. If hdmiphy is stable
/linux-4.1.27/Documentation/filesystems/
Dqnx6.txt44 (or period) and building up a new (stable) filesystem structure under the
166 at the same time there is still a complete stable filesystem structer in the
172 stable declared - superblock.
Dpath-lookup.txt91 and this stabilises its d_inode pointer and actual inode. This gives a stable
179 taking a reference count (the reference count then gives a stable place to
225 Where ref-walk uses a stable, refcounted ``parent'' to walk the remaining
299 lookups, and to assume dentry mount points and mount roots are stable up and
Ddebugfs.txt7 there. The debugfs filesystem is also intended to not serve as a stable
Dsysfs.txt378 this ABI is stable and properly documented. All new sysfs attributes must be
Dxfs.txt222 namespace is on stable storage. This is useful in HA setups
Dramfs-rootfs-initramfs.txt241 http://www.linuxfromscratch.org/lfs/view/stable/
Dvfs.txt445 filesystems such as NFS where page cache is not stable
693 a file, the file must have a stable mapping to a block
Dproc.txt891 NFS_Unstable: NFS pages sent to the server, but not yet committed to stable
/linux-4.1.27/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra20-pmc.txt41 - nvidia,core-pwr-good-time : <Oscillator-stable-time Power-stable-time>
/linux-4.1.27/Documentation/i2c/muxes/
Di2c-mux-gpio80 Alternatively, if you don't need a stable device name, you can simply
/linux-4.1.27/Documentation/sound/alsa/
DBt87x.txt29 The driver is now stable. However, it doesn't know about many TV cards,
/linux-4.1.27/fs/nfsd/
Dxdr3.h41 int stable; member
Dnfsproc.c161 int stable = 1; in nfsd_proc_write() local
172 &stable); in nfsd_proc_write()
Dnfs3proc.c191 argp->stable? " stable" : ""); in nfsd3_proc_write()
194 resp->committed = argp->stable; in nfsd3_proc_write()
Dvfs.c958 int stable = *stablep; in nfsd_vfs_write() local
979 stable = 0; in nfsd_vfs_write()
991 if (stable) { in nfsd_vfs_write()
Dnfs3xdr.c368 args->stable = ntohl(*p++); in nfs3svc_decode_writeargs()
/linux-4.1.27/
DREPORTING-BUGS6 kernel, any "stable" kernel versions, and any "long term" kernels.
14 Alternatively, you can attempt to run one of the supported stable or -rc
DREADME88 (also known as the -stable kernels) are not incremental but instead apply
244 less stable by configuring some routines to actively try to
DMAINTAINERS9385 L: stable@vger.kernel.org
/linux-4.1.27/Documentation/sound/oss/
Dbtaudio30 Still somewhat experimental. The driver should work stable, i.e. it
/linux-4.1.27/Documentation/pti/
Dpti_intel_mid.txt21 a stable, reliable connection that will not break unless
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME.freeze36 0.7.x. I have no idea where exactly, it works stable for me and a lot of
/linux-4.1.27/Documentation/cpu-freq/
Dcpu-drivers.txt84 and target_intermediate Used to switch to stable frequency while
206 get_intermediate should return a stable intermediate frequency platform wants to
/linux-4.1.27/Documentation/acpi/
Dvideo_extension.txt22 Documentation/ABI/stable/sysfs-class-backlight.
/linux-4.1.27/fs/nfs/
Dnfs4_fs.h340 hdr->args.stable = NFS_FILE_SYNC; in nfs4_state_protect_write()
Dpagelist.c584 hdr->args.stable = NFS_UNSTABLE; in nfs_pgio_rpcsetup()
592 hdr->args.stable = NFS_FILE_SYNC; in nfs_pgio_rpcsetup()
Dwrite.c1438 if (hdr->res.verf->committed < hdr->args.stable && in nfs_writeback_done()
1455 hdr->res.verf->committed, hdr->args.stable); in nfs_writeback_done()
1504 argp->stable = NFS_FILE_SYNC; in nfs_writeback_result()
Dproc.c621 hdr->args.stable = NFS_FILE_SYNC; in nfs_proc_write_setup()
Dnfs3xdr.c1004 *p++ = cpu_to_be32(args->stable); in encode_write3args()
Dnfs4xdr.c1697 *p++ = cpu_to_be32(args->stable); in encode_write()
/linux-4.1.27/Documentation/s390/
Dkvm.txt3 the interface to the module is not yet considered to remain stable. Thus, be
/linux-4.1.27/Documentation/scsi/
Dtmscsim.txt47 the next revisions will be 2.0a to 2.0X (stable), 2.1a to 2.1X (experimental),
48 2.2a to 2.2X (stable, again) etc. (X = anything between a and z.) If I send
90 proven stable on many systems, but it's still a good idea to take some
Dosst.txt181 platform such an interesting, nice and stable platform.
DChangeLog.megaraid405 are actually used. It is now mandatory for GCC 3.4.1 (current stable)
DChangeLog.1992-1997552 is not stable under heavy load. Race condition and all that.
/linux-4.1.27/Documentation/gpio/
Dsysfs.txt113 what purposes. However, those numbers are not always stable; GPIOs on
Dgpio-legacy.txt732 what purposes. However, those numbers are not always stable; GPIOs on
/linux-4.1.27/Documentation/vm/
Dhwpoison.txt121 Note these injection interfaces are not stable and might change between
/linux-4.1.27/Documentation/arm/
Dkernel_user_helpers.txt14 guaranteed to be stable.
/linux-4.1.27/Documentation/filesystems/nfs/
DExporting14 form of reference needs to be stable across renames, truncates, and
/linux-4.1.27/Documentation/fb/
Dudlfb.txt109 more stable, and higher performance.
Dintel810.txt155 more stable setup, but will be slower.
Dframebuffer.txt202 stable picture without visible flicker, VESA recommends a vertical scanrate of
/linux-4.1.27/Documentation/virtual/kvm/
Dtimekeeping.txt265 Although in theory the APIC is a safe and stable source for local interrupts,
405 not be a stable time source, and must be calibrated against a known, stable,
Dapi.txt97 This identifies the API version as the stable kvm API. It is not
/linux-4.1.27/fs/affs/
DChanges4 then, 3.1 doesn't mean 'perfectly stable', too.)
/linux-4.1.27/arch/powerpc/platforms/
DKconfig269 relatively stable. If you say Y here, a single temperature value,
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt35 shall be as stable and correct as possible as compared to a real-world wall
/linux-4.1.27/drivers/edac/
DKconfig71 WARNING: Do not even assume this interface is staying stable!
/linux-4.1.27/Documentation/ioctl/
Dbotching-up-ioctls.txt212 disclaimer of not having a stable ABI would be better.
/linux-4.1.27/include/linux/
Dnfs_xdr.h517 enum nfs3_stable_how stable; /* used by write */ member
/linux-4.1.27/drivers/ide/
DKconfig289 Please note that this method of assuring stable naming of
311 Please also note that this method of assuring stable naming of
/linux-4.1.27/fs/befs/
DChangeLog218 seems stable and not outragously slow. Existing features are more-or-less
/linux-4.1.27/Documentation/usb/
Dproc_usb_info.txt49 you can't rely on them for stable access to devices. For example,
Dusb-serial.txt215 part stable and has been tested on an smp machine. (dual p2)
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-decoder-regs.txt291 more unstable it becomes. Decoder output remains stable.
/linux-4.1.27/drivers/scsi/aacraid/
Daacraid.h1431 __le32 stable; // Not used member
/linux-4.1.27/Documentation/kdump/
Dkdump.txt453 Before analyzing the dump image, you should reboot into a stable kernel.
/linux-4.1.27/mm/
DKconfig303 # We also use the bounce pool to provide stable page writes for jbd. jbd
/linux-4.1.27/arch/x86/kvm/
Dx86.c7200 bool stable, backwards_tsc = false; in kvm_arch_hardware_enable() local
7208 stable = !check_tsc_unstable(); in kvm_arch_hardware_enable()
7211 if (!stable && vcpu->cpu == smp_processor_id()) in kvm_arch_hardware_enable()
7213 if (stable && vcpu->arch.last_host_tsc > local_tsc) { in kvm_arch_hardware_enable()
/linux-4.1.27/drivers/input/keyboard/
DKconfig274 However, it has been thoroughly tested and is stable.
/linux-4.1.27/Documentation/cgroups/
Dmemory.txt849 Overall, the memory controller has been a stable controller and has been
/linux-4.1.27/Documentation/power/
Ddevices.txt470 an image of the system memory while everything is stable, reactivate all
/linux-4.1.27/arch/x86/
DKconfig735 The HPET provides a stable time base on SMP
757 The APBT provides a stable time base on SMP
/linux-4.1.27/drivers/hwmon/
DKconfig1635 on them being stable.
/linux-4.1.27/lib/
DKconfig.debug1272 kernel less stable. It can also greatly increase grace-period