From: Zi Yan <ziy@nvidia.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Brendan Jackman <jackmanb@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add missing files to mm page alloc section
Date: Wed, 18 Jun 2025 07:10:39 -0400 [thread overview]
Message-ID: <DD279102-8AFD-4987-86FB-7A5C4738C1C1@nvidia.com> (raw)
In-Reply-To: <20250618105953.67630-1-lorenzo.stoakes@oracle.com>
On 18 Jun 2025, at 6:59, 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>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Acked-by: Brendan Jackman <jackmanb@google.com>
> ---
>
> RFC:
> https://lore.kernel.org/all/20250616202425.563581-1-lorenzo.stoakes@oracle.com/
>
> MAINTAINERS | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index bbabcb161572..40ff84e1dcd1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15875,8 +15875,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
Acked-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-06-18 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 10:59 Lorenzo Stoakes
2025-06-18 11:10 ` Zi Yan [this message]
2025-06-18 14:16 ` David Hildenbrand
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=DD279102-8AFD-4987-86FB-7A5C4738C1C1@nvidia.com \
--to=ziy@nvidia.com \
--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=vbabka@suse.cz \
/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