korg/linux
0
0
Fork 0
mirror of https://mirrors.bfsu.edu.cn/git/linux.git synced 2024-11-28 22:54:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: stable-kernel-rules: mention other usages for stable tag comments

Browse Source 
Document how to delay backporting or send a note to the stable team
using shell-style inline comments attached to stable tags.

CC: Greg KH <gregkh@linuxfoundation.org>
CC: Sasha Levin <sashal@kernel.org>
CC: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
Link: https://lore.kernel.org/r/bf1489b40ff358b7cb4f7d8cc73d5c7c3c143471.1689056247.git.linux@leemhuis.info
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Thorsten Leemhuis 2023-07-11 08:19:53 +02:00 committed by Greg Kroah-Hartman
parent d2e8071bed
commit d0bde9ca0e
1 changed files with 19 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
Documentation/process/stable-kernel-rules.rst
View File

@ -55,9 +55,10 @@ To have the patch automatically included in the stable tree, add the tag
Cc: stable@vger.kernel.org Cc: stable@vger.kernel.org
in the sign-off area. Once the patch is merged it will be applied to in the sign-off area. To accompany a note to the stable team, use a shell-style
the stable tree without anything else needing to be done by the author inline comment (see below for details). Once the patch is merged it will be
or subsystem maintainer. applied to the stable tree without anything else needing to be done by the
author or subsystem maintainer.
.. _option_2: .. _option_2:
@ -139,6 +140,21 @@ The tag has the meaning of:
For each "-stable" tree starting with the specified version. For each "-stable" tree starting with the specified version.
To delay pick up of patches submitted via :ref:`option_1`, use the following
format:
.. code-block:: none
Cc: <stable@vger.kernel.org> # after 4 weeks in mainline
For any other requests related to patches submitted via :ref:`option_1`, just
add a note to the stable tag. This for example can be used to point out known
problems:
.. code-block:: none
Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for >= 6.3
Following the submission: Following the submission:
- The sender will receive an ACK when the patch has been accepted into the - The sender will receive an ACK when the patch has been accepted into the