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