Lines Matching full:stable

116 Documentation/process/stable-kernel-rules.rst already explain in more detail:
130    the fix for backporting using the ``Cc: stable@vger.kernel.org`` tag.
166    mainline, stable, or longterm release (either directly or via backport).
179    particular hardware environment, distribution, or stable/longterm series.
182    into a recent mainline, stable, or longterm release (either directly or via
209    subsystem maintainer might be unavailable. Also CC the stable team, when you
210    know such a regression made it into a mainline, stable, or longterm release.
224 Regarding stable and longterm kernels:
226  * You are free to leave regressions to the stable team, if they at no point in
230    twelve months, ensure to tag the fix with "Cc: stable@vger.kernel.org", as a
232    in case you know the culprit was backported to stable or longterm kernels.
234  * When receiving reports about regressions in recent stable or longterm kernel
240    into a proper mainline, stable, or longterm release, fix it quickly in
242    above). That's because the stable team normally does neither revert nor fix
246    backporting by dropping the stable team a note once the fix was mainlined;
382 repositories of linux-next, mainline, and stable/longterm.
772        re-introduced (perhaps even backported as a stable patch) once we have