linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: stable@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [RFC PATCH v1 1/3] docs: stable-kernel-rules: mention other usages for stable tag comments
Date: Mon, 10 Jul 2023 21:43:41 +0200	[thread overview]
Message-ID: <2023071003-slab-underling-2b50@gregkh> (raw)
In-Reply-To: <d30686781c47c83927e0a41f6a1167a679fa822c.1689008220.git.linux@leemhuis.info>

On Mon, Jul 10, 2023 at 07:10:11PM +0200, Thorsten Leemhuis wrote:
> 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>
> ---
>  Documentation/process/stable-kernel-rules.rst | 22 ++++++++++++++++---
>  1 file changed, 19 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index 51df1197d5ab..6e4026dd6882 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -55,9 +55,10 @@ To have the patch automatically included in the stable tree, add the tag
>  
>       Cc: stable@vger.kernel.org
>  
> -in the sign-off area. Once the patch is merged it will be applied to
> -the stable tree without anything else needing to be done by the author
> -or subsystem maintainer.
> +in the sign-off area; to accompany a note to the stable team, use a shell-style

Is that how a ';' is really used?  I never can remember, so it's an
honest question here :)

> +inline comment (see below for details). Once the patch is merged it will be
> +applied to the stable tree without anything else needing to be done by the
> +author or subsystem maintainer.
>  
>  .. _option_2:
>  
> @@ -139,6 +140,21 @@ The tag has the meaning of:
>  
>  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
> +

This looks great to me, so I'll be glad to take it.

thanks,

greg k-h

  reply	other threads:[~2023-07-10 19:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 17:10 [RFC PATCH v1 0/3] docs: stable-kernel-rules: add delayed backporting option and a few tweaks Thorsten Leemhuis
2023-07-10 17:10 ` [RFC PATCH v1 1/3] docs: stable-kernel-rules: mention other usages for stable tag comments Thorsten Leemhuis
2023-07-10 19:43   ` Greg KH [this message]
2023-07-11  6:07     ` Thorsten Leemhuis
2023-07-11 10:15   ` Jani Nikula
2023-07-11 10:33     ` Thorsten Leemhuis
2023-07-10 17:10 ` [RFC PATCH v1 2/3] docs: stable-kernel-rules: make rule section more straight forward Thorsten Leemhuis
2023-07-10 19:44   ` Greg KH
2023-07-10 17:10 ` [RFC PATCH v1 3/3] docs: stable-kernel-rules: improve structure to optimize reading flow Thorsten Leemhuis
2023-07-10 19:46   ` Greg KH
2023-07-10 17:18 ` [RFC PATCH v1 0/3] docs: stable-kernel-rules: add delayed backporting option and a few tweaks Thorsten Leemhuis
2023-07-10 19:50   ` Greg KH
2023-07-11  5:57     ` Thorsten Leemhuis
2023-07-11  8:42   ` Johan Hovold
2023-07-11  8:57     ` Thorsten Leemhuis
2023-07-10 19:51 ` Greg KH
2023-07-12  9:30   ` Thorsten Leemhuis
2023-07-12 15:16     ` Greg KH
2023-07-12 17:02       ` Thorsten Leemhuis
2023-07-12 19:00         ` Greg KH
2023-07-13  8:48           ` Thorsten Leemhuis
2023-07-13 15:06             ` Greg KH
2023-07-13 15:39               ` Conor Dooley
2023-07-13 16:27                 ` Thorsten Leemhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2023071003-slab-underling-2b50@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).