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 this tag in the sign-off area::
73   Cc: stable@vger.kernel.org
75 Use ``Cc: stable@kernel.org`` instead when fixing unpublished vulnerabilities:
79 Once the patch is mainlined it will be applied to the stable tree without
82 To send additional instructions to the stable team, use a shell-style inline
87     Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
88     Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
89     Cc: <stable@vger.kernel.org> # 3.3.x: fd21073: sched: Fix affinity logic
90     Cc: <stable@vger.kernel.org> # 3.3.x
108   prerequisite of patch2 if you have already marked patch1 for stable
113     Cc: <stable@vger.kernel.org> # 3.3.x
119   For each "-stable" tree starting with the specified version.
121   Note, such tagging is unnecessary if the stable team can derive the
126     Cc: <stable@vger.kernel.org> # after -rc3
130     Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
132 There furthermore is a variant of the stable tag you can use to make the stable
136      Cc: <stable[email protected]> # reason goes here, and must be present
144 stable@vger.kernel.org containing the subject of the patch, the commit ID,
154 stable@vger.kernel.org and mention the kernel versions you wish it to be applied
174 days, according to the schedules of the stable team members.
176 If accepted, the patch will be added to the -stable queue, for review by other
183 - When the -stable maintainers decide for a review cycle, the patches will be
200 - At the end of the review cycle, the new -stable release will be released
202 - Security patches will be accepted into the -stable tree directly from the
213     https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
215 - The finalized and tagged releases of all stable kernels can be found
218     https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
220 - The release candidate of all stable kernel versions can be found at:
222     https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
225      The -stable-rc tree is a snapshot in time of the stable-queue tree and