From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Workflows <workflows@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] Documentation: process: Also mention Sasha Levin as stable tree maintainer
Date: Wed, 22 Oct 2025 10:30:44 -0700 [thread overview]
Message-ID: <2997d8b9-a37a-4411-a5d8-b2cfcc3944b8@infradead.org> (raw)
In-Reply-To: <20251022034336.22839-1-bagasdotme@gmail.com>
On 10/21/25 8:43 PM, Bagas Sanjaya wrote:
> Sasha has also maintaining stable branch in conjunction with Greg
> since cb5d21946d2a2f ("MAINTAINERS: Add Sasha as a stable branch
> maintainer"). Mention him in 2.Process.rst.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Now matches the MAINTAINERS file.
Thanks.
> ---
> Documentation/process/2.Process.rst | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/process/2.Process.rst b/Documentation/process/2.Process.rst
> index 8e63d171767db8..7bd41838a5464f 100644
> --- a/Documentation/process/2.Process.rst
> +++ b/Documentation/process/2.Process.rst
> @@ -99,8 +99,10 @@ go out with a handful of known regressions, though, hopefully, none of them
> are serious.
>
> Once a stable release is made, its ongoing maintenance is passed off to the
> -"stable team," currently Greg Kroah-Hartman. The stable team will release
> -occasional updates to the stable release using the 9.x.y numbering scheme.
> +"stable team," currently consists of Greg Kroah-Hartman and Sasha Levin. The
> +stable team will release occasional updates to the stable release using the
> +9.x.y numbering scheme.
> +
> To be considered for an update release, a patch must (1) fix a significant
> bug, and (2) already be merged into the mainline for the next development
> kernel. Kernels will typically receive stable updates for a little more
>
> base-commit: 0aa760051f4eb3d3bcd812125557bd09629a71e8
--
~Randy
next prev parent reply other threads:[~2025-10-22 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 3:43 Bagas Sanjaya
2025-10-22 5:11 ` Greg Kroah-Hartman
2025-10-22 17:30 ` Randy Dunlap [this message]
2025-10-29 16:08 ` Jonathan Corbet
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=2997d8b9-a37a-4411-a5d8-b2cfcc3944b8@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=workflows@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