mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>, Zi Yan <ziy@nvidia.com>,
	Suren Baghdasaryan <surenb@google.com>,
	Brendan Jackman <jackmanb@google.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add missing files to mm page alloc section
Date: Tue, 17 Jun 2025 20:32:02 +0200	[thread overview]
Message-ID: <86f2e9c0-3cee-4062-b18d-d86b10393a63@suse.cz> (raw)
In-Reply-To: <20250616202425.563581-1-lorenzo.stoakes@oracle.com>

On 6/16/25 22:24, Lorenzo Stoakes wrote:
> There are a number of files within memory management which appear to be
> most suitably placed within the page allocation section of MAINTAINERS and
> are otherwise unassigned, so place these there.
> 
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> REVIEWERS - let me know if these seem appropriate, I'm eyeballing
> this. even if they are not quite best placed a 'best effort' is still
> worthwhile so we establish a place to put all mm files, we can always
> incrementally update these later.

All look relevant enough to me, well spotted.

Acked-by: Vlastimil Babka <vbabka@suse.cz>

> 
>  MAINTAINERS | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4523a6409186..58136a57b7a6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15856,8 +15856,17 @@ F:	include/linux/compaction.h
>  F:	include/linux/gfp.h
>  F:	include/linux/page-isolation.h
>  F:	mm/compaction.c
> +F:	mm/debug_page_alloc.c
> +F:	mm/fail_page_alloc.c
>  F:	mm/page_alloc.c
> +F:	mm/page_ext.c
> +F:	mm/page_frag_cache.c
>  F:	mm/page_isolation.c
> +F:	mm/page_owner.c
> +F:	mm/page_poison.c
> +F:	mm/page_reporting.c
> +F:	mm/show_mem.c
> +F:	mm/shuffle.c
> 
>  MEMORY MANAGEMENT - RECLAIM
>  M:	Andrew Morton <akpm@linux-foundation.org>
> --
> 2.49.0


  reply	other threads:[~2025-06-17 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 20:24 Lorenzo Stoakes
2025-06-17 18:32 ` Vlastimil Babka [this message]
2025-06-18 10:57   ` Lorenzo Stoakes
2025-06-18  9:56 ` Brendan Jackman
2025-06-18 10:57   ` Lorenzo Stoakes

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=86f2e9c0-3cee-4062-b18d-d86b10393a63@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@kernel.org \
    --cc=surenb@google.com \
    --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

all inboxes | Powered by JetHome®