From: Andrew Morton <akpm@linux-foundation.org>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
Yu Zhao <yuzhao@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark MGLRU as maintained
Date: Fri, 15 Aug 2025 22:32:56 -0700 [thread overview]
Message-ID: <20250815223256.111f6ce04da3528fdf19ae84@linux-foundation.org> (raw)
In-Reply-To: <22qegz4vktquv22nome6csd4vngvwcaeydoyg3ttqoal5vum27@knjvryszxbdm>
On Fri, 15 Aug 2025 17:08:59 -0700 Shakeel Butt <shakeel.butt@linux.dev> wrote:
> > > > +MEMORY MANAGEMENT - MGLRU (MULTI-GEN LRU)
> > >
> > > Why not just add yourselves (and the missing files) to the existing
> > > reclaim section? Eventually we want a single reclaim solution, so why
> > > not start with single reviewer section?
> >
> > Sure, I can see the argument for that.
> >
> > I suppose the case against would be, perhaps the folks already listed
> > in the RECLAIM section don't want to additionally get e-mail for the
> > extra files listed in this patch? (Perhaps mostly the MGLRU
> > documentation, the rest of them aren't necessarily MGLRU specific.)
> >
> > I don't have a strong preference either way, I think mostly I'd be
> > interested to know Andrew's or the other reviewers' preference. Note
> > Lorenzo suggested a separate MGLRU section here:
> > https://lkml.org/lkml/2025/8/14/271
> >
>
> I would not be too worried about folks getting emails for MGLRU. Anyways
> whatever Andrew decides is fine with me.
We all like lots of emails, don't we?
I don't know, the main thing is to get it in there - we can fine-tune
things later if desired.
prev parent reply other threads:[~2025-08-16 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 21:59 [PATCH] MAINTAINERS: mark MGLRU as maintained Axel Rasmussen
2025-08-15 23:13 ` Shakeel Butt
2025-08-15 23:40 ` Axel Rasmussen
2025-08-16 0:08 ` Shakeel Butt
2025-08-16 5:32 ` Andrew Morton [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=20250815223256.111f6ce04da3528fdf19ae84@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=yuzhao@google.com \
/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;
as well as URLs for NNTP newsgroup(s).