* [PATCH] linux-next: update maintainer info.
@ 2026-02-16 6:07 Randy Dunlap
2026-02-16 9:16 ` Stephen Rothwell
0 siblings, 1 reply; 4+ messages in thread
From: Randy Dunlap @ 2026-02-16 6:07 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, Stephen Rothwell, Mark Brown, Jonathan Corbet,
Shuah Khan, workflows, linux-doc
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] linux-next: update maintainer info.
2026-02-16 6:07 [PATCH] linux-next: update maintainer info Randy Dunlap
@ 2026-02-16 9:16 ` Stephen Rothwell
2026-02-16 15:37 ` Mark Brown
2026-02-20 17:14 ` Shuah Khan
0 siblings, 2 replies; 4+ messages in thread
From: Stephen Rothwell @ 2026-02-16 9:16 UTC (permalink / raw)
To: Randy Dunlap
Cc: linux-kernel, Mark Brown, Jonathan Corbet, Shuah Khan, workflows,
linux-doc
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] linux-next: update maintainer info.
2026-02-16 9:16 ` Stephen Rothwell
@ 2026-02-16 15:37 ` Mark Brown
2026-02-20 17:14 ` Shuah Khan
1 sibling, 0 replies; 4+ messages in thread
From: Mark Brown @ 2026-02-16 15:37 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Randy Dunlap, linux-kernel, Jonathan Corbet, Shuah Khan,
workflows, linux-doc
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Mon, Feb 16, 2026 at 08:16:48PM +1100, Stephen Rothwell wrote:
> On Sun, 15 Feb 2026 22:07:39 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> > 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>
You've escaped! :P
Acked-by: Mark Brown <broonie@kernel.org>
> Maybe update the CREDITS file? ;-)
Good idea..
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] linux-next: update maintainer info.
2026-02-16 9:16 ` Stephen Rothwell
2026-02-16 15:37 ` Mark Brown
@ 2026-02-20 17:14 ` Shuah Khan
1 sibling, 0 replies; 4+ messages in thread
From: Shuah Khan @ 2026-02-20 17:14 UTC (permalink / raw)
To: Stephen Rothwell, Randy Dunlap
Cc: linux-kernel, Mark Brown, Jonathan Corbet, workflows, linux-doc,
Shuah Khan
On 2/16/26 02:16, Stephen Rothwell wrote:
> 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? ;-)
Thank you Stephen for shepherding linux-next all these years and
keeping us all sane. You will be missed. Good luck with your next
adventure.
thanks,
-- Shuah
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-02-20 17:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-02-16 6:07 [PATCH] linux-next: update maintainer info Randy Dunlap
2026-02-16 9:16 ` Stephen Rothwell
2026-02-16 15:37 ` Mark Brown
2026-02-20 17:14 ` Shuah Khan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox