Lines Matching refs:stable

3 Everything you ever wanted to know about Linux -stable releases
7 "-stable" tree:
35 Procedure for submitting patches to the -stable tree
40    Security patches should not be handled (solely) by the -stable review
52 To have the patch automatically included in the stable tree, add the tag
56      Cc: stable@vger.kernel.org
59 the stable tree without anything else needing to be done by the author
68 stable@vger.kernel.org containing the subject of the patch, the commit ID,
78 stable@vger.kernel.org.  You must note the upstream commit ID in the
112      Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
113      Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
114      Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
115      Cc: <stable@vger.kernel.org> # 3.3.x
132      Cc: <stable@vger.kernel.org> # 3.3.x
140 For each "-stable" tree starting with the specified version.
147  - If accepted, the patch will be added to the -stable queue, for review by
154  - When the -stable maintainers decide for a review cycle, the patches will be
171  - At the end of the review cycle, the new -stable release will be released
173  - Security patches will be accepted into the -stable tree directly from the
183 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
185  - The finalized and tagged releases of all stable kernels can be found
188 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
190  - The release candidate of all stable kernel versions can be found at:
192         https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
195       The -stable-rc tree is a snapshot in time of the stable-queue tree and