Lines Matching full:stable
3 Everything you ever wanted to know about Linux -stable releases
7 "-stable" tree:
35 Procedure for submitting patches to the -stable tree
38 - Security patches should not be handled (solely) by the -stable review
50 To have the patch automatically included in the stable tree, add the tag
54 Cc: stable@vger.kernel.org
57 the stable tree without anything else needing to be done by the author
66 stable@vger.kernel.org containing the subject of the patch, the commit ID,
76 stable@vger.kernel.org. You must note the upstream commit ID in the
104 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
105 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
106 Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
107 Cc: <stable@vger.kernel.org> # 3.3.x
124 Cc: <stable@vger.kernel.org> # 3.3.x
132 For each "-stable" tree starting with the specified version.
139 - If accepted, the patch will be added to the -stable queue, for review by
146 - When the -stable maintainers decide for a review cycle, the patches will be
155 latest -stable release, and a new -stable release will happen.
156 - Security patches will be accepted into the -stable tree directly from the
166 https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
168 - The finalized and tagged releases of all stable kernels can be found
171 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git