From: SeongJae Park <sj@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add mm-related procfs files to MM sections
Date: Thu, 5 Mar 2026 17:34:52 -0800 [thread overview]
Message-ID: <20260306013453.90906-1-sj@kernel.org> (raw)
In-Reply-To: <20260305-maintainers-proc-v1-1-d6d09b3db3b6@kernel.org>
On Thu, 05 Mar 2026 09:26:29 +0100 "Vlastimil Babka (SUSE)" <vbabka@kernel.org> wrote:
> Some procfs files are very much related to memory management so let's
> have MAINTAINERS reflect that.
>
> Add fs/proc/meminfo.c to MEMORY MANAGEMENT - CORE.
>
> Add fs/proc/task_[no]mmu.c to MEMORY MAPPING.
>
> Signed-off-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
I have a few trivial comments below. Regardless of those,
Acked-by: SeongJae Park <sj@kernel.org>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3553554019e8..39987895bcfc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -16683,6 +16683,7 @@ F: include/linux/ptdump.h
> F: include/linux/vmpressure.h
> F: include/linux/vmstat.h
> F: include/trace/events/zone_lock.h
> +F: fs/proc/meminfo.c
Should we sort files alphabetically, and hence put this before 'include/...' ?
I see a few other MAINTAINERS sections including 'MEMORY MANGEMENT -
USERFAULTFD' are doing so. I have no strong opinion, though.
> F: kernel/fork.c
> F: mm/Kconfig
> F: mm/debug.c
> @@ -16998,6 +16999,8 @@ S: Maintained
> W: http://www.linux-mm.org
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> F: include/trace/events/mmap.h
> +F: fs/proc/task_mmu.c
> +F: fs/proc/task_nommu.c
Ditto.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-03-06 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 8:26 [PATCH] MAINTAINERS: add mm-related procfs files to MM sections Vlastimil Babka (SUSE)
2026-03-05 8:30 ` Lorenzo Stoakes (Oracle)
2026-03-05 8:31 ` Mike Rapoport
2026-03-05 8:46 ` David Hildenbrand (Arm)
2026-03-06 1:34 ` SeongJae Park [this message]
2026-03-06 8:04 ` Vlastimil Babka (SUSE)
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=20260306013453.90906-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.