From: Josh Law <joshlaw48@gmail.com>
To: akpm@linux-foundation.org
Cc: david@kernel.org, linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] MM transition
Date: Tue, 21 Apr 2026 20:25:24 +0100 [thread overview]
Message-ID: <16B7B5A8-EEA7-4580-A565-3A0B4DBB08AB@gmail.com> (raw)
In-Reply-To: <20260421094216.8dfe14a8c62f2420fa5aace1@linux-foundation.org>
Hello, since I'm not coming to LSF/BPF because of my age (aw)
(And I'm more than aware this post is more mm focused, but I'm
representing lib :))
I'm "virtually" putting my hand up
Whats going to happen to lib/?
I'm aware there are submaintainers for some files
E.G: Steven (and Petr) for vsprintf
Masami for bootconfig
Willy for idr
Liam for maple tree
Etc
But let's say, lib/glob.c, or lib/bug.c, even lib/inflate.c! (And/or
all files which only has you set as primary maintainer)
get_maintainers.pl says just you!
If you retire, let's say, then the files will be orphaned, idk what
you want to do with these files.
Thanks! :-)
prev parent reply other threads:[~2026-04-21 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 16:42 Andrew Morton
2026-04-21 19:25 ` Josh Law [this message]
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=16B7B5A8-EEA7-4580-A565-3A0B4DBB08AB@gmail.com \
--to=joshlaw48@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.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