From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>
Cc: Alexander Graf <graf@amazon.com>,
Alexander Potapenko <glider@google.com>,
Brendan Jackman <jackmanb@google.com>,
Christoph Lameter <cl@gentwo.org>,
Dennis Zhou <dennis@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>, Marco Elver <elver@google.com>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Tejun Heo <tj@kernel.org>, Uladzislau Rezki <urezki@gmail.com>,
Vlastimil Babka <vbabka@kernel.org>, Zi Yan <ziy@nvidia.com>,
kasan-dev@googlegroups.com, kexec@lists.infradead.org,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 0/3] mm: split a couple of headers from internal.h
Date: Thu, 09 Jul 2026 09:41:46 +0300 [thread overview]
Message-ID: <20260709-internal-h-v1-0-956d5092782d@kernel.org> (raw)
mm/internal.h becomes more and more bloated.
Split declarations related to mm_init, memblock, vmalloc and sparse into
new headers.
---
Mike Rapoport (Microsoft) (3):
mm: split out mm_init and memblock declarations from internal.h
mm: split out sparse declarations from internal.h
mm: split out vmalloc declarations from internal.h
MAINTAINERS | 3 +
kernel/liveupdate/kexec_handover.c | 3 +-
mm/cma.c | 1 +
mm/execmem.c | 1 +
mm/hugetlb.c | 1 +
mm/internal.h | 183 -------------------------------------
mm/kmsan/hooks.c | 1 +
mm/kmsan/shadow.c | 1 +
mm/memblock.c | 1 +
mm/memory_hotplug.c | 1 +
mm/mm_init.c | 3 +
mm/mm_init.h | 120 ++++++++++++++++++++++++
mm/page_alloc.c | 1 +
mm/percpu-vm.c | 1 +
mm/sparse-vmemmap.c | 2 +
mm/sparse.c | 2 +
mm/sparse.h | 63 +++++++++++++
mm/vmalloc.c | 1 +
mm/vmalloc.h | 46 ++++++++++
19 files changed, 251 insertions(+), 184 deletions(-)
---
base-commit: 820d5dfede0cd55dcbc89ce96fcfbb11b7c457ba
change-id: 20260707-internal-h-2efef660381d
--
Sincerely yours,
Mike.
next reply other threads:[~2026-07-09 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 6:41 Mike Rapoport (Microsoft) [this message]
2026-07-09 6:41 ` [PATCH 1/3] mm: split out mm_init and memblock declarations from internal.h Mike Rapoport (Microsoft)
2026-07-09 6:41 ` [PATCH 2/3] mm: split out sparse " Mike Rapoport (Microsoft)
2026-07-09 6:41 ` [PATCH 3/3] mm: split out vmalloc " Mike Rapoport (Microsoft)
2026-07-09 7:22 ` [PATCH 0/3] mm: split a couple of headers " Mike Rapoport
2026-07-09 7:48 ` Muchun Song
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=20260709-internal-h-v1-0-956d5092782d@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=david@kernel.org \
--cc=dennis@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=graf@amazon.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kexec@lists.infradead.org \
--cc=liam@infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.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