Re: [PATCH] MAINTAINERS: mark MGLRU as maintained

[Shakeel Butt <shakeel.butt@linux.dev>]

On Fri, Aug 15, 2025 at 04:40:26PM -0700, Axel Rasmussen wrote:
> On Fri, Aug 15, 2025 at 4:13 PM Shakeel Butt <shakeel.butt@linux.dev> wrote:
> >
> > On Fri, Aug 15, 2025 at 02:59:14PM -0700, Axel Rasmussen wrote:
> > > The three folks being added here are actively working on MGLRU within
> > > Google, so we can review patches for this feature and plan to contribute
> > > some improvements / extensions to it on an ongoing basis.
> > >
> > > With three of us we may have some hope filling Yu Zhao's shoes, since he
> > > has moved on to other projects these days.
> > >
> > > Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
> > > ---
> > >  MAINTAINERS | 17 +++++++++++++++++
> > >  1 file changed, 17 insertions(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index daf520a13bdf..8e987f2668cd 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -16058,6 +16058,23 @@ F:   mm/mempolicy.c
> > >  F:   mm/migrate.c
> > >  F:   mm/migrate_device.c
> > >
> > > +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.