From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
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>, Pavel Machek <pavel@denx.de>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH] Documentation: process: Describe kernel version prefix for third option
Date: Tue, 1 Nov 2022 14:30:45 +0100 [thread overview]
Message-ID: <Y2EfhWxk0j/oVLJx@kroah.com> (raw)
In-Reply-To: <20221101131743.371340-1-bagasdotme@gmail.com>
On Tue, Nov 01, 2022 at 08:17:43PM +0700, Bagas Sanjaya wrote:
> The current wording on third option of stable kernel submission doesn't
> mention how to specify desired kernel version. Submitters reading the
> documentation could simply send multiple backported patches of the same
> upstream commit without any kernel version information, leaving stable
> maintainers and reviewers hard time to figure out the correct kernel
> version to be applied.
>
> Describe the subject prefix for specifying kernel version for the case
> above.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> This patch is sent as response to [1].
>
> [1]: https://lore.kernel.org/stable/20221101074351.GA8310@amd/
>
> Documentation/process/stable-kernel-rules.rst | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index 2fd8aa593a2851..409ae73c1ffcd1 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -77,7 +77,9 @@ Option 3
> Send the patch, after verifying that it follows the above rules, to
> stable@vger.kernel.org. You must note the upstream commit ID in the
> changelog of your submission, as well as the kernel version you wish
> -it to be applied to.
> +it to be applied to by adding desired kernel version number to the
> +patch subject prefix. For example, patches targeting 5.15 kernel should
> +have ``[PATCH 5.15]`` prefix.
No, sorry, this is not needed and does not have to be in the subject
line at all.
The current wording is fine, it's just that people don't always read it.
so consider this a NAK.
thanks,
greg k-h-
next prev parent reply other threads:[~2022-11-01 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:17 Bagas Sanjaya
2022-11-01 13:30 ` Greg Kroah-Hartman [this message]
2022-11-02 4:19 ` Bagas Sanjaya
2022-11-02 4:59 ` Greg Kroah-Hartman
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=Y2EfhWxk0j/oVLJx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@denx.de \
--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
all inboxes | Powered by JetHome®