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
38  - If the patch covers files in net/ or drivers/net please follow netdev stable
41  - Security patches should not be handled (solely) by the -stable review
53 To have the patch automatically included in the stable tree, add the tag
57      Cc: stable@vger.kernel.org
60 the stable tree without anything else needing to be done by the author
69 stable@vger.kernel.org containing the subject of the patch, the commit ID,
79 stable@vger.kernel.org.  You must note the upstream commit ID in the
107      Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
108      Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
109      Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
110      Cc: <stable@vger.kernel.org> # 3.3.x
127      Cc: <stable@vger.kernel.org> # 3.3.x
135 For each "-stable" tree starting with the specified version.
142  - If accepted, the patch will be added to the -stable queue, for review by
149  - When the -stable maintainers decide for a review cycle, the patches will be
158    latest -stable release, and a new -stable release will happen.
159  - Security patches will be accepted into the -stable tree directly from the
169 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
171  - The finalized and tagged releases of all stable kernels can be found
174 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git