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
109      Cc: <stable@vger.kernel.org> # 3.3.x
117    For each "-stable" tree starting with the specified version.
119    Note, such tagging is unnecessary if the stable team can derive the
126      Cc: <stable@vger.kernel.org> # after 4 weeks in mainline
128  * For any other requests, just add a note to the stable tag. This for example
133      Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
141 stable@vger.kernel.org containing the subject of the patch, the commit ID,
151 stable@vger.kernel.org and mention the kernel versions you wish it to be applied
175 days, according to the schedules of the stable team members.
177 If accepted, the patch will be added to the -stable queue, for review by other
184  - When the -stable maintainers decide for a review cycle, the patches will be
201  - At the end of the review cycle, the new -stable release will be released
203  - Security patches will be accepted into the -stable tree directly from the
214 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
216  - The finalized and tagged releases of all stable kernels can be found
219 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
221  - The release candidate of all stable kernel versions can be found at:
223         https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
226       The -stable-rc tree is a snapshot in time of the stable-queue tree and