Lines Matching refs:stable
1 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
72 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
73 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
74 Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
75 Cc: <stable@vger.kernel.org> # 3.3.x
87 Cc: <stable@vger.kernel.org> # 3.3.x-
92 For each "-stable" tree starting with the specified version.
99 - If accepted, the patch will be added to the -stable queue, for review by
105 - When the -stable maintainers decide for a review cycle, the patches will be
114 latest -stable release, and a new -stable release will happen.
115 - Security patches will be accepted into the -stable tree directly from the
123 http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git
124 - The finalized and tagged releases of all stable kernels can be found
126 http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git