Lines Matching full:stable
20 Are you facing a regression with vanilla kernels from the same stable or
22 <https://lore.kernel.org/lkml/>`_ and the `Linux stable mailing list
23 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
25 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
26 mailing list (stable@vger.kernel.org) and CC the regressions list
39 supported stable or longterm series as well? Then install its latest release.
110 * If you are facing a regression within a stable or longterm version line
112 'Dealing with regressions within a stable and longterm kernel line'.
127 the latest 'stable' Linux can be an acceptable alternative in some
139 stable and longterm kernels.
177 Reporting regressions within a stable and longterm kernel line
181 the point about regression within a stable or longterm kernel version line. You
192 * Check the archives of the `Linux stable mailing list
193 <https://lore.kernel.org/stable/>`_ for existing reports.
201 * Send a short problem report to the Linux stable mailing list
202 (stable@vger.kernel.org) and CC the Linux regressions mailing list
217 see the issue fixed in a still supported stable or longterm series or vendor
225 within a stable and longterm kernel line" above.
238 as the stable mailing list.
323 with kernels from distributions shipping the latest stable kernel, as long as
326 want to use a mainline Linux and avoid using a stable kernel for this
589 Regression in stable or longterm kernel?
592 *If you are facing a regression within a stable or longterm version line
594 'Dealing with regressions within a stable and longterm kernel line'.*
596 Regression within a stable and longterm kernel version line are something the
790 the latest 'stable' Linux can be an acceptable alternative in some
808 * Install a mainline kernel; the latest stable kernel can be an option, but
846 latest stable version offered on kernel.org. Using that is also acceptable in
851 Better avoid using the latest stable kernel outside merge windows, as all fixes
877 latest mainline or stable Linux built as vanilla kernel. It's totally okay to
881 are older than a week, as new mainline and stable kernels typically get released
944 stable and longterm kernels.*
949 users might still be plagued by it, as long as it's not fixed in either stable
1063 regression in a stable or longterm kernel, avoid testing versions which number
1302 tagging it for later backport to stable and longterm kernels that need it. Then
1478 Reference for "Reporting regressions within a stable and longterm kernel line"
1482 a regression within a stable and longterm kernel line.
1498 Note, if kernel.org lists two stable version lines on the front page, you
1505 Search stable mailing list
1508 *Check the archives of the Linux stable mailing list for existing reports.*
1511 `search the archives of the Linux stable mailing list
1512 <https://lore.kernel.org/stable/>`_ for reports about an issue like yours. If
1543 *Send a short problem report to the Linux stable mailing list
1544 (stable@vger.kernel.org) and CC the Linux regressions mailing list
1551 When reporting a regression that happens within a stable or longterm kernel
1554 stable and regressions mailing list is all it takes; but in case you suspect
1585 version lines (aka stable and longterm kernels).
1595 totally unexpected problems. The maintainers of the stable and longterm kernels
1597 within rules outlined in 'Documentation/process/stable-kernel-rules.rst'.
1600 to mainline. Other fixes are easy to get backported to the newest stable and
1619 * Search the Linux stable mailing list for exiting reports.
1648 'stable tag' that looks like this:
1650 Cc: <stable@vger.kernel.org> # 5.4+
1672 * If the fix doesn't contain a stable tag and backporting was not discussed,
1683 as the stable mailing list.*
1688 for the subsystem as well as the stable mailing list (stable@vger.kernel.org).