From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux-kernel Mailing List <linux-kernel@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>,
Linus Torvalds <torvalds@linux-foundation•org>
Subject: Re: linux-next: changing maintainership
Date: Thu, 18 Dec 2025 08:52:04 +0000 [thread overview]
Message-ID: <df68e9a1-2b98-423d-915d-58f224db6374@sirena.org.uk> (raw)
In-Reply-To: <20251218180721.20eb878e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Thu, Dec 18, 2025 at 06:07:21PM +1100, Stephen Rothwell wrote:
> Some of you already know this, but this is a general announcement.
> I will be stepping down as Linux-Next maintainer on Jan 16, 2026. Mark
> Brown has generously volunteered to take up the challenge. He has
> helped in the past filling in when I have been unavailable, so
> hopefully knows what he is getting in to. I hope you will all treat
> him with the same (or better) level of respect that I have received.
> It has been a long but mostly interesting task and I hope it has been
> helpful to others. It seems a long time since I read Andrew Morton's
> "I have a dream" email and decided that I could help out there - little
> did I know what I was heading for.
> I hope to still be around the kernel community, but just not so active.
Thanks Stephen for all your work over the many years you've been doing
-next, these are certainly going to be big shoes to try to fill.
Thanks also to Arm for agreeing to support me doing this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-18 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 7:07 linux-next: changing maintainership Stephen Rothwell
2025-12-18 8:52 ` Mark Brown [this message]
2025-12-19 10:53 ` Miguel Ojeda
2025-12-19 11:56 ` Krzysztof Kozlowski
2026-01-12 23:28 ` Stephen Rothwell
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=df68e9a1-2b98-423d-915d-58f224db6374@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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