From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <ljs@kernel.org>
Cc: 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,
"Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Subject: [PATCH] MAINTAINERS: add mm-related procfs files to MM sections
Date: Thu, 05 Mar 2026 09:26:29 +0100 [thread overview]
Message-ID: <20260305-maintainers-proc-v1-1-d6d09b3db3b6@kernel.org> (raw)
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>
---
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
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
F: mm/interval_tree.c
F: mm/mincore.c
F: mm/mlock.c
---
base-commit: 7fcd8889fbf318409163ff5033fe161dd2a73243
change-id: 20260305-maintainers-proc-30e45ca9e434
Best regards,
--
Vlastimil Babka (SUSE) <vbabka@kernel.org>
next reply other threads:[~2026-03-05 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 8:26 Vlastimil Babka (SUSE) [this message]
2026-03-05 8:30 ` Lorenzo Stoakes (Oracle)
2026-03-05 8:31 ` Mike Rapoport
2026-03-05 8:46 ` David Hildenbrand (Arm)
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=20260305-maintainers-proc-v1-1-d6d09b3db3b6@kernel.org \
--to=vbabka@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 \
/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