public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Josh Law <joshlaw48@gmail.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] MM transition
Date: Wed, 22 Apr 2026 20:18:25 +0200	[thread overview]
Message-ID: <92c3d650-be80-4a64-a962-3586ba753316@kernel.org> (raw)
In-Reply-To: <16B7B5A8-EEA7-4580-A565-3A0B4DBB08AB@gmail.com>

On 4/21/26 21:25, Josh Law wrote:
> 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)

I'd assume that (excluding MM bits, for example) falls in the foreseeable future
under the "I plan to keep running the mm-nonmm branches.".

What happens when Andrew fully retires is a probably a good question for the
future :)

-- 
Cheers,

David


  reply	other threads:[~2026-04-22 18:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 16:42 [LSF/MM/BPF TOPIC] MM transition Andrew Morton
2026-04-21 19:25 ` Josh Law
2026-04-22 18:18   ` David Hildenbrand (Arm) [this message]
2026-04-22 18:22     ` Josh Law
2026-04-22 18:44       ` David Hildenbrand (Arm)
2026-04-22 18:48         ` Josh Law
2026-04-22 19:03   ` Matthew Wilcox
2026-04-22 19:13     ` Josh Law

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=92c3d650-be80-4a64-a962-3586ba753316@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=joshlaw48@gmail.com \
    --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