From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Subject: [PATCH v2] MAINTAINERS: add MM MISC section, add missing files to MISC and CORE
Date: Wed, 23 Jul 2025 10:58:23 +0100 [thread overview]
Message-ID: <20250723095823.21940-1-lorenzo.stoakes@oracle.com> (raw)
Add a MEMORY MANAGEMENT - MISC section to contain files that are not described
by other sections, moving all but the catch-all mm/ and tools/mm/ from MEMORY
MANAGEMENT to MEMORY MANAGEMENT - CORE and MEMORY MANAGEMENT - MISC as
appropriate.
In both sections add remaining missing files. At this point, with the other
recent MAINTAINERS changes, this should now mean that every memory
management-related file has a section and assigned maintainers/reviewers.
Finally, we copy across the maintainers/reviewers from MEMORY MANAGEMENT -
CORE to MEMORY MANAGEMENT - MISC, as it seems the two are sufficiently
related for this to be sensible.
Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
---
v2:
* Propagate ack (thanks Mike!)
* Retain MEMORY MANAGEMENT section to contain the global mm/ and tools/mm/
directories and remove from MEMORY MANAGEMENT - MISC section, I misunderstood
how these catch-alls would work. As reported by Vlastimil.
* Update cover letter and subject to reflect the above.
v1:
https://lore.kernel.org/all/20250722192704.164758-1-lorenzo.stoakes@oracle.com/
MAINTAINERS | 68 ++++++++++++++++++++++++++++++++++++++++++-----------
1 file changed, 54 insertions(+), 14 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 507a999f1955..5a9d4c57add4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15741,22 +15741,8 @@ S: Maintained
W: http://www.linux-mm.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
T: quilt git://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new
-F: Documentation/admin-guide/mm/
-F: Documentation/mm/
-F: include/linux/gfp.h
-F: include/linux/gfp_types.h
-F: include/linux/memory_hotplug.h
-F: include/linux/memory-tiers.h
-F: include/linux/mempolicy.h
-F: include/linux/mempool.h
-F: include/linux/mmzone.h
-F: include/linux/mmu_notifier.h
-F: include/linux/pagewalk.h
-F: include/trace/events/ksm.h
F: mm/
F: tools/mm/
-F: tools/testing/selftests/mm/
-N: include/linux/page[-_]*
MEMORY MANAGEMENT - CORE
M: Andrew Morton <akpm@linux-foundation.org>
@@ -15771,18 +15757,32 @@ L: linux-mm@kvack.org
S: Maintained
W: http://www.linux-mm.org
T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
+F: include/linux/gfp.h
+F: include/linux/gfp_types.h
F: include/linux/memory.h
F: include/linux/mm.h
F: include/linux/mm_*.h
+F: include/linux/mmzone.h
F: include/linux/mmdebug.h
F: include/linux/pagewalk.h
F: kernel/fork.c
F: mm/Kconfig
F: mm/debug.c
+F: mm/folio-compat.c
+F: mm/highmem.c
F: mm/init-mm.c
+F: mm/internal.h
+F: mm/maccess.c
F: mm/memory.c
+F: mm/mmzone.c
F: mm/pagewalk.c
+F: mm/pgtable-generic.c
+F: mm/sparse-vmemmap.c
+F: mm/sparse.c
F: mm/util.c
+F: mm/vmpressure.c
+F: mm/vmstat.c
+N: include/linux/page[-_]*
MEMORY MANAGEMENT - EXECMEM
M: Andrew Morton <akpm@linux-foundation.org>
@@ -15844,6 +15844,46 @@ F: mm/mempolicy.c
F: mm/migrate.c
F: mm/migrate_device.c
+MEMORY MANAGEMENT - MISC
+M: Andrew Morton <akpm@linux-foundation.org>
+M: David Hildenbrand <david@redhat.com>
+R: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
+R: Liam R. Howlett <Liam.Howlett@oracle.com>
+R: Vlastimil Babka <vbabka@suse.cz>
+R: Mike Rapoport <rppt@kernel.org>
+R: Suren Baghdasaryan <surenb@google.com>
+R: Michal Hocko <mhocko@suse.com>
+L: linux-mm@kvack.org
+S: Maintained
+W: http://www.linux-mm.org
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
+F: Documentation/admin-guide/mm/
+F: Documentation/mm/
+F: include/linux/memory-tiers.h
+F: include/linux/mempolicy.h
+F: include/linux/mempool.h
+F: include/linux/memremap.h
+F: include/linux/mmu_notifier.h
+F: include/trace/events/ksm.h
+F: mm/backing-dev.c
+F: mm/cma.c
+F: mm/cma_debug.c
+F: mm/cma_sysfs.c
+F: mm/dmapool.c
+F: mm/dmapool_test.c
+F: mm/early_ioremap.c
+F: mm/fadvise.c
+F: mm/io-mapping.c
+F: mm/ioremap.c
+F: mm/mapping_dirty_helpers.c
+F: mm/memory-tiers.c
+F: mm/mmu_notifier.c
+F: mm/page_idle.c
+F: mm/pgalloc-track.h
+F: mm/process_vm_access.c
+F: mm/ptdump.c
+F: tools/testing/selftests/mm/
+
MEMORY MANAGEMENT - NUMA MEMBLOCKS AND NUMA EMULATION
M: Andrew Morton <akpm@linux-foundation.org>
M: Mike Rapoport <rppt@kernel.org>
--
2.50.1
next reply other threads:[~2025-07-23 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 9:58 Lorenzo Stoakes [this message]
2025-07-23 10:36 ` David Hildenbrand
2025-07-23 10:50 ` Lorenzo Stoakes
2025-07-23 10:42 ` David Hildenbrand
2025-07-23 15:05 ` Lorenzo Stoakes
2025-07-23 15:13 ` Vlastimil Babka
2025-07-23 15:20 ` Lorenzo Stoakes
2025-07-23 15:32 ` 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=20250723095823.21940-1-lorenzo.stoakes@oracle.com \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rppt@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