From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Alistair Popple <apopple@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Baoquan He <baoquan.he@linux.dev>,
Barry Song <baohua@kernel.org>,
Brendan Jackman <brendan.jackman@linux.dev>,
Byungchul Park <byungchul@sk.com>,
Chengming Zhou <chengming.zhou@linux.dev>,
Chris Li <chrisl@kernel.org>, Christoph Lameter <cl@gentwo.org>,
Dave Chinner <david@fromorbit.com>,
David Rientjes <rientjes@google.com>,
Dennis Zhou <dennis@kernel.org>, Dev Jain <dev.jain@arm.com>,
Gregory Price <gourry@gourry.net>, Hao Li <hao.li@linux.dev>,
Harry Yoo <harry@kernel.org>, Hugh Dickins <hughd@google.com>,
Jann Horn <jannh@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
John Hubbard <jhubbard@nvidia.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Kairui Song <kasong@tencent.com>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Kiryl Shutsemau <kas@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Matthew Brost <matthew.brost@intel.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Michal Hocko <mhocko@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Nhat Pham <nphamcs@gmail.com>, Nick Piggin <npiggin@gmail.com>,
Nico Pache <nico.pache@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Pedro Falcato <pfalcato@suse.de>, Peter Xu <peterx@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Qi Zheng <qi.zheng@linux.dev>, Rakie Kim <rakie.kim@sk.com>,
Rik van Riel <riel@surriel.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Suren Baghdasaryan <surenb@google.com>,
Tejun Heo <tj@kernel.org>, Uladzislau Rezki <urezki@gmail.com>,
Usama Arif <usama.arif@linux.dev>,
Vlastimil Babka <vbabka@kernel.org>,
Will Deacon <will@kernel.org>, Xu Xin <xu.xin@linux.dev>,
Ying Huang <ying.huang@linux.alibaba.com>,
Youngjun Park <youngjun.park@lge.com>, Zi Yan <ziy@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"David Hildenbrand (Arm)" <david@kernel.org>
Subject: [PATCH 0/7] MAINTAINERS: MM updates
Date: Fri, 30 Oct 2026 22:34:24 +0100 [thread overview]
Message-ID: <20261030-maintainers-v1-0-97278f8a5f54@kernel.org> (raw)
Hi,
several MM updates:
Make Zi Yan a THP maintainer (thanks for all your hard work over
the years and thanks for taking on this responsibility), and perform some
MM MAINTAINERS cleanups.
Then, start the next step of the transition from Andrew's MM tree to
separate component trees that all get integrated into the mm-next
integration tree.
Start routing shmem through mm/core.git, adding me as a maintainer
primarily to pick patches.
Then, target the following components for the mm/core.git tree that I
(co)maintain:
- MEMORY MANAGEMENT - BALLOON
- MEMORY MANAGEMENT - CORE
- MEMORY MANAGEMENT - GUP (GET USER PAGES)
- MEMORY MANAGEMENT - KSM (Kernel Samepage Merging)
- MEMORY MANAGEMENT - MEMORY HOT(UN)PLUG
- MEMORY MANAGEMENT - MIGRATION
- MEMORY MANAGEMENT - NUMA PLACEMENT
- MEMORY MANAGEMENT - RMAP (REVERSE MAPPING)
- MEMORY MANAGEMENT - THP (TRANSPARENT HUGE PAGE)
More details in the last patch.
In the upcoming cycles we'll then route more of the other MM components
through different trees.
Let's see how this goes, in particular with the continuous stream of
fixes. But getting these in in a controlled way has highest priority
right now wither way.
Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
---
David Hildenbrand (Arm) (7):
MAINTAINERS: mention for-next branch in MEMORY MANAGEMENT - MEMORY MAP
MAINTAINERS: TMPFS (SHMEM FILESYSTEM) updates
MAINTAINERS: add Zi Yan as co-maintainer for MEMORY MANAGEMENT - THP
MAINTAINERS: sort entries in MM sections
MAINTAINERS: add missing files to MM component sections
MAINTAINERS: rename and move MEMORY HOT(UN)PLUG
MAINTAINERS: route more MM changes through mm/core.git
MAINTAINERS | 165 ++++++++++++++++++++++++++++++++++++++----------------------
1 file changed, 105 insertions(+), 60 deletions(-)
---
base-commit: d89e1d186ec9271bf78e62771779e9fc03bf0fc3
change-id: 20261029-maintainers-e2699bff7521
--
Cheers,
David
next reply other threads:[~2026-10-30 21:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 21:34 David Hildenbrand (Arm) [this message]
2026-10-30 21:34 ` [PATCH 1/7] MAINTAINERS: mention for-next branch in MEMORY MANAGEMENT - MEMORY MAP David Hildenbrand (Arm)
2026-10-31 0:40 ` Muchun Song
2026-10-31 8:38 ` Lorenzo Stoakes (ARM)
2026-10-30 21:34 ` [PATCH 2/7] MAINTAINERS: TMPFS (SHMEM FILESYSTEM) updates David Hildenbrand (Arm)
2026-10-31 8:42 ` Lorenzo Stoakes (ARM)
2026-10-30 21:34 ` [PATCH 3/7] MAINTAINERS: add Zi Yan as co-maintainer for MEMORY MANAGEMENT - THP David Hildenbrand (Arm)
2026-10-30 22:00 ` Zi Yan
2026-10-30 23:33 ` Barry Song
2026-10-31 0:39 ` Muchun Song
2026-10-31 4:01 ` Lance Yang
2026-10-31 5:43 ` Dev Jain
2026-10-31 8:36 ` Lorenzo Stoakes (ARM)
2026-10-30 21:34 ` [PATCH 4/7] MAINTAINERS: sort entries in MM sections David Hildenbrand (Arm)
2026-10-30 21:34 ` [PATCH 5/7] MAINTAINERS: add missing files to MM component sections David Hildenbrand (Arm)
2026-10-31 0:42 ` Muchun Song
2026-10-30 21:34 ` [PATCH 6/7] MAINTAINERS: rename and move MEMORY HOT(UN)PLUG David Hildenbrand (Arm)
2026-10-31 0:43 ` Muchun Song
2026-10-30 21:34 ` [PATCH 7/7] MAINTAINERS: route more MM changes through mm/core.git David Hildenbrand (Arm)
2026-10-30 22:02 ` [PATCH 0/7] MAINTAINERS: MM updates Zi Yan
2026-10-30 23:48 ` SJ Park
2026-10-31 7:49 ` Qi Zheng
2026-10-31 8:30 ` Mike Rapoport
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=20261030-maintainers-v1-0-97278f8a5f54@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=brendan.jackman@linux.dev \
--cc=byungchul@sk.com \
--cc=chengming.zhou@linux.dev \
--cc=chrisl@kernel.org \
--cc=cl@gentwo.org \
--cc=david@fromorbit.com \
--cc=dennis@kernel.org \
--cc=dev.jain@arm.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=matthew.brost@intel.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=nico.pache@linux.dev \
--cc=nphamcs@gmail.com \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=pfalcato@suse.de \
--cc=qi.zheng@linux.dev \
--cc=rakie.kim@sk.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=will@kernel.org \
--cc=xu.xin@linux.dev \
--cc=ying.huang@linux.alibaba.com \
--cc=youngjun.park@lge.com \
--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
all inboxes | Powered by JetHome®