From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] linux-next: update maintainer info.
Date: Mon, 16 Feb 2026 20:16:48 +1100 [thread overview]
Message-ID: <20260216091648.7a6a0e3a@canb.auug.org.au> (raw)
In-Reply-To: <20260216060739.2791462-1-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
Hi Randy,
On Sun, 15 Feb 2026 22:07:39 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Update the MAINTAINERS file and Documentation/process/2.Process.rst
> with the current linux-next maintainer information.
>
> Translations of 2.Process.rst should also be updated.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: workflows@vger.kernel.org
> Cc: linux-doc@vger.kernel.org
>
> Documentation/process/2.Process.rst | 2 +-
> MAINTAINERS | 1 -
> 2 files changed, 1 insertion(+), 2 deletions(-)
>
> --- linux-next-20260213.orig/Documentation/process/2.Process.rst
> +++ linux-next-20260213/Documentation/process/2.Process.rst
> @@ -291,7 +291,7 @@ Use of the MMOTM tree is likely to be a
> there is a definite chance that it will not even compile.
>
> The primary tree for next-cycle patch merging is linux-next, maintained by
> -Stephen Rothwell. The linux-next tree is, by design, a snapshot of what
> +Mark Brown. The linux-next tree is, by design, a snapshot of what
> the mainline is expected to look like after the next merge window closes.
> Linux-next trees are announced on the linux-kernel and linux-next mailing
> lists when they are assembled; they can be downloaded from:
> --- linux-next-20260213.orig/MAINTAINERS
> +++ linux-next-20260213/MAINTAINERS
> @@ -14749,7 +14749,6 @@ F: Documentation/memory-barriers.txt
> F: tools/memory-model/
>
> LINUX-NEXT TREE
> -M: Stephen Rothwell <sfr@canb.auug.org.au>
> M: Mark Brown <broonie@kernel.org>
> L: linux-next@vger.kernel.org
> S: Supported
Acked-by: Stephen Rothwell <sfr@canb.auug.org.au>
Maybe update the CREDITS file? ;-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-02-16 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 6:07 Randy Dunlap
2026-02-16 9:16 ` Stephen Rothwell [this message]
2026-02-16 15:37 ` Mark Brown
2026-02-20 17:14 ` Shuah Khan
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=20260216091648.7a6a0e3a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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