linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yuanchu Xie <yuanchu@google.com>
To: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	 Kairui Song <kasong@tencent.com>, Qi Zheng <qi.zheng@linux.dev>,
	 Shakeel Butt <shakeel.butt@linux.dev>,
	Barry Song <baohua@kernel.org>,
	 Axel Rasmussen <axelrasmussen@google.com>,
	Wei Xu <weixugc@google.com>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update MGLRU entry to reflect current status
Date: Fri, 27 Mar 2026 16:15:09 -0500	[thread overview]
Message-ID: <CAJj2-QG-z9uETNMeWmnp_F3BoVM1up9q1W3NO8-MJ9ddehVXQw@mail.gmail.com> (raw)
In-Reply-To: <20260326185629.355476-1-ljs@kernel.org>

On Thu, Mar 26, 2026 at 1:56 PM Lorenzo Stoakes (Oracle) <ljs@kernel.org> wrote:
>
> We are moving to a far more proactive model of maintainership within mm and
> thus put a great deal of emphasis on sub-maintainers being active within
> the community both in terms of code contributions and review.
>
> The MGLRU has not had much activity since being added to the kernel and the
> current maintainers who kindly stepped up have unfortunately not been able
> to contribute a great deal to it for over a year, nor engage all that
> heavily in review.
>
> As a result, and within no negative connotations implied whatsoever, it
> seems appropriate to downgrade the current maintainers to reviewers.
>
> At this time nobody is quite exercising the maintainer role in this area of
> the kernel, but there is encouraging activity from a number of people who
> are trusted elsewhere in the kernel, and who have contributed relevant work
> or review.
>
> Therefore add further reviewers, and at this stage - to reflect the reality
> on the ground - we will not have any sub-maintainers listed at all.
>
> Each of the files listed are shared with other sections in MAINTAINERS, so
> this doesn't reduce sub-maintainer coverage.
Yep, thanks for proposing this change. That all makes sense to me.

Acked-by: Yuanchu Xie <yuanchu@google.com>


  parent reply	other threads:[~2026-03-27 21:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 18:56 Lorenzo Stoakes (Oracle)
2026-03-26 19:09 ` Vlastimil Babka (SUSE)
2026-03-26 19:27   ` David Hildenbrand (Arm)
2026-03-26 23:47   ` Suren Baghdasaryan
2026-03-27  0:26     ` Kalesh Singh
2026-03-27  7:47       ` Lorenzo Stoakes (Oracle)
2026-03-26 23:12 ` Barry Song
2026-03-27  0:02 ` SeongJae Park
2026-03-27  2:13 ` Kairui Song
2026-03-27  2:52 ` Qi Zheng
2026-03-27 21:15 ` Yuanchu Xie [this message]
2026-03-30  0:31 ` Shakeel Butt
2026-03-30  9:35   ` Lorenzo Stoakes (Oracle)
     [not found] <20260326185428.354430-1-ljs@kernel.org>
     [not found] ` <CAJHvVcjAm9MLvmHA9SWQzGirM-9HJ4qpDQ263Ku+EUJH+bxY1w@mail.gmail.com>
2026-03-26 20:41   ` Lorenzo Stoakes (Oracle)

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=CAJj2-QG-z9uETNMeWmnp_F3BoVM1up9q1W3NO8-MJ9ddehVXQw@mail.gmail.com \
    --to=yuanchu@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=david@kernel.org \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=qi.zheng@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=weixugc@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