linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	David Hildenbrand <david@redhat.com>, Zi Yan <ziy@nvidia.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	Suren Baghdasaryan <surenb@google.com>,
	Brendan Jackman <jackmanb@google.com>,
	Michal Hocko <mhocko@kernel.org>
Subject: Re: [RFC PATCH 2/2] MAINTAINERS: add MM subsection for the page allocator
Date: Mon, 7 Apr 2025 21:56:13 +0100	[thread overview]
Message-ID: <Z_Q77Xi-_zeSYyrJ@casper.infradead.org> (raw)
In-Reply-To: <20250407200508.121357-4-vbabka@suse.cz>

On Mon, Apr 07, 2025 at 10:05:10PM +0200, Vlastimil Babka wrote:
> Extra reviewers would be welcome, including/not limited the people I
> Cc'd based on my recollection and get_maintainers --git
> Also if I missed any related file please lmk. Thanks.

I appreciate the offer.  I feel entirely unqualified to review patches
to the page allocator, although I'll probably end up touching it quite
a lot when we move to separately allocated folios.


  parent reply	other threads:[~2025-04-07 20:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 20:05 [RFC PATCH 1/2] MAINTAINERS: update SLAB ALLOCATOR maintainers Vlastimil Babka
2025-04-07 20:05 ` [RFC PATCH 2/2] MAINTAINERS: add MM subsection for the page allocator Vlastimil Babka
2025-04-07 20:12   ` Zi Yan
2025-04-07 20:14     ` Vlastimil Babka
2025-04-07 20:56   ` Matthew Wilcox [this message]
2025-04-08  0:03   ` Johannes Weiner
2025-04-08  9:34   ` Michal Hocko
2025-04-08 14:12   ` Brendan Jackman
2025-04-08 16:43     ` Suren Baghdasaryan
2025-04-08 18:52   ` David Hildenbrand
2025-04-07 20:21 ` [RFC PATCH 1/2] MAINTAINERS: update SLAB ALLOCATOR maintainers Harry Yoo
2025-04-08 16:43   ` Christoph Lameter (Ampere)
2025-04-08 20:27   ` David Rientjes

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=Z_Q77Xi-_zeSYyrJ@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=ziy@nvidia.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