Lines Matching full:stable

3 Everything you ever wanted to know about Linux -stable releases
7 "-stable" tree:
34 Procedure for submitting patches to the -stable tree
39    Security patches should not be handled (solely) by the -stable review
43 There are three options to submit a change to -stable trees:
45  1. Add a 'stable tag' to the description of a patch you then submit for
47  2. Ask the stable team to pick up a patch already mainlined.
48  3. Submit a patch to the stable team that is equivalent to a change already
60 stable series. When doing so, ensure the fix or an equivalent is applicable,
61 submitted, or already present in all newer stable trees still supported. This is
71 for stable trees, add the tag
75      Cc: stable@vger.kernel.org
78 stable tree without anything else needing to be done by the author or
81 To sent additional instructions to the stable team, use a shell-style inline
89      Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
90      Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
91      Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
92      Cc: <stable@vger.kernel.org> # 3.3.x
114    prerequisite of patch2 if you have already marked patch1 for stable
122      Cc: <stable@vger.kernel.org> # 3.3.x
130    For each "-stable" tree starting with the specified version.
132    Note, such tagging is unnecessary if the stable team can derive the
139      Cc: <stable@vger.kernel.org> # after 4 weeks in mainline
141  * For any other requests, just add a note to the stable tag. This for example
146      Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
154 stable@vger.kernel.org containing the subject of the patch, the commit ID,
164 stable@vger.kernel.org and mention the kernel versions you wish it to be applied
188 days, according to the schedules of the stable team members.
190 If accepted, the patch will be added to the -stable queue, for review by other
197  - When the -stable maintainers decide for a review cycle, the patches will be
214  - At the end of the review cycle, the new -stable release will be released
216  - Security patches will be accepted into the -stable tree directly from the
227 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
229  - The finalized and tagged releases of all stable kernels can be found
232 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
234  - The release candidate of all stable kernel versions can be found at:
236         https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
239       The -stable-rc tree is a snapshot in time of the stable-queue tree and