linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Vlastimil Babka <vbabka@suse.cz>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	Brendan Jackman <jackmanb@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] MAINTAINERS: add missing files to page alloc section
Date: Tue, 22 Jul 2025 13:42:46 -0400	[thread overview]
Message-ID: <F551AD99-F191-453D-8115-F37E0A74EE65@nvidia.com> (raw)
In-Reply-To: <20250722174143.147143-1-lorenzo.stoakes@oracle.com>

On 22 Jul 2025, at 13:41, Lorenzo Stoakes wrote:

> There are a couple of mm/-specific header files that were accidentally
> missed previously, and some page ref debug code also that ought to live
> here.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
>  MAINTAINERS | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 837bc5cd6166..703f176315d5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15879,6 +15879,7 @@ F:	include/linux/gfp.h
>  F:	include/linux/page-isolation.h
>  F:	mm/compaction.c
>  F:	mm/debug_page_alloc.c
> +F:	mm/debug_page_ref.c
>  F:	mm/fail_page_alloc.c
>  F:	mm/page_alloc.c
>  F:	mm/page_ext.c
> @@ -15887,8 +15888,10 @@ F:	mm/page_isolation.c
>  F:	mm/page_owner.c
>  F:	mm/page_poison.c
>  F:	mm/page_reporting.c
> +F:	mm/page_reporting.h
>  F:	mm/show_mem.c
>  F:	mm/shuffle.c
> +F:	mm/shuffle.h
>
>  MEMORY MANAGEMENT - RECLAIM
>  M:	Andrew Morton <akpm@linux-foundation.org>
> -- 
> 2.50.1

Acked-by: Zi Yan <ziy@nvidia.com>

Best Regards,
Yan, Zi


  reply	other threads:[~2025-07-22 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 17:41 Lorenzo Stoakes
2025-07-22 17:42 ` Zi Yan [this message]
2025-07-22 19:53 ` David Hildenbrand
2025-07-23  9:24 ` Vlastimil Babka

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=F551AD99-F191-453D-8115-F37E0A74EE65@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@suse.com \
    --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