From: David Hildenbrand <david@redhat.com>
To: Shakeel Butt <shakeel.butt@linux.dev>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>, Yu Zhao <yuzhao@google.com>,
Qi Zheng <zhengqi.arch@bytedance.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add mm reclaim section
Date: Thu, 8 May 2025 20:31:28 +0200 [thread overview]
Message-ID: <7d214c08-56ef-45c7-9ba3-18d7e4691efd@redhat.com> (raw)
In-Reply-To: <mhnz33dwwd3npj2re7dn7invntzk6dk7u75ue2pzg35vdappjd@tgqlccmoydar>
On 08.05.25 20:30, Shakeel Butt wrote:
> On Thu, May 08, 2025 at 06:37:35PM +0100, Lorenzo Stoakes wrote:
>> In furtherance of ongoing efforts to ensure people are aware of who
>> de-facto maintains/has an interest in specific parts of mm, as well trying
>> to avoid get_maintainers.pl listing only Andrew and the mailing list for mm
>> files - establish a reclaim memory management section and add relevant
>> maintainers/reviewers.
>>
>> This is a key part of memory management so sensibly deserves its own
>> section.
>>
>> This encompasses both 'classical' reclaim and MGLRU and thus reflects this
>> in the reviewers from both, as well as those who have contributed
>> specifically on the memcg side of things.
>>
>> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>
> Seems fine to me, though I would put Johannes as M (if he is fine with
> it).
That would be lovely.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-05-08 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 17:37 Lorenzo Stoakes
2025-05-08 17:40 ` David Hildenbrand
2025-05-08 18:27 ` Johannes Weiner
2025-05-08 18:30 ` Shakeel Butt
2025-05-08 18:31 ` David Hildenbrand [this message]
2025-05-09 5:32 ` Johannes Weiner
2025-05-09 8:43 ` Lorenzo Stoakes
2025-05-09 2:58 ` Qi Zheng
2025-05-12 11:49 ` Lorenzo Stoakes
2025-05-12 7:54 ` Michal Hocko
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=7d214c08-56ef-45c7-9ba3-18d7e4691efd@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.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