]> git.ipfire.org Git - thirdparty/kernel/linux.git/commitdiff
linux-next: update maintainer info.
authorRandy Dunlap <rdunlap@infradead.org>
Mon, 16 Feb 2026 06:07:39 +0000 (22:07 -0800)
committerJonathan Corbet <corbet@lwn.net>
Mon, 23 Feb 2026 21:36:11 +0000 (14:36 -0700)
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>
Acked-by: Stephen Rothwell <sfr@canb.auug.org.au>
Acked-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20260216060739.2791462-1-rdunlap@infradead.org>

Documentation/process/2.Process.rst
MAINTAINERS

index 57fa8cac58a6e7c059315eba0eac5193887190bc..77f3f80e7cd7e1766f91e9da6c2a654a1c6e7776 100644 (file)
@@ -291,7 +291,7 @@ Use of the MMOTM tree is likely to be a frustrating experience, though;
 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:
index 202abb8a789d6afa4d9457f7f46d31b41ce54de9..c05a72245049a46c9e0f9b3b04e6a109da597bbf 100644 (file)
@@ -14748,7 +14748,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