From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>, Matthew Brost <matthew.brost@intel.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Byungchul Park <byungchul@sk.com>,
Gregory Price <gourry@gourry.net>,
Ying Huang <ying.huang@linux.alibaba.com>,
Alistair Popple <apopple@nvidia.com>,
Rakie Kim <rakie.kim@sk.com>, Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH 0/3] MAINTAINERS: rework MEMORY MANAGEMENT - MEMORY POLICY AND MIGRATION
Date: Mon, 21 Sep 2026 09:28:22 +0200 [thread overview]
Message-ID: <3e9ce58a-1316-48a0-9bab-715c70d117f6@kernel.org> (raw)
In-Reply-To: <20260918-maintainers-mempolicy-v1-0-9a94cac6d135@kernel.org>
On 9/18/26 18:34, David Hildenbrand (Arm) wrote:
> Let's rework MEMORY MANAGEMENT - MEMORY POLICY AND MIGRATION.
>
> As I can use some maintenance help in that area, add Gregory as
> a new co-maintainer for the split out MEMORY MANAGEMENT - NUMA PLACEMENT
> section.
>
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
> David Hildenbrand (Arm) (3):
> MAINTAINERS: split up MEMORY MANAGEMENT - MEMORY POLICY AND MIGRATION
> MAINTAINERS: move memory tiering under MEMORY MANAGEMENT - NUMA PLACEMENT
> MAINTAINERS: make Gregory a co-maintainer of MEMORY MANAGEMENT - NUMA PLACEMENT
Great, thanks David and Gregory!
Acked-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
>
> MAINTAINERS | 68 ++++++++++++++++++++++++++++++++++++-------------------------
> 1 file changed, 40 insertions(+), 28 deletions(-)
>
> ---
>
> base-commit: 5dd1818b15d98d4a20806cd00b1b40320b06004f
>
> change-id: 20260918-maintainers-mempolicy-06bf34b59ec3
>
> --
>
> Cheers,
>
> David
>
prev parent reply other threads:[~2026-09-21 7:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 16:34 David Hildenbrand (Arm)
2026-09-18 16:34 ` [PATCH 1/3] MAINTAINERS: split up " David Hildenbrand (Arm)
2026-09-18 16:37 ` Lorenzo Stoakes (ARM)
2026-09-18 16:56 ` Zi Yan
2026-09-19 0:48 ` SJ Park
2026-09-18 16:34 ` [PATCH 2/3] MAINTAINERS: move memory tiering under MEMORY MANAGEMENT - NUMA PLACEMENT David Hildenbrand (Arm)
2026-09-18 16:39 ` Lorenzo Stoakes (ARM)
2026-09-18 16:57 ` Zi Yan
2026-09-19 0:50 ` SJ Park
2026-09-18 16:34 ` [PATCH 3/3] MAINTAINERS: make Gregory a co-maintainer of " David Hildenbrand (Arm)
2026-09-18 16:41 ` Lorenzo Stoakes (ARM)
2026-09-18 16:41 ` Gregory Price
2026-09-19 10:06 ` David Hildenbrand (Arm)
2026-09-18 16:57 ` Zi Yan
2026-09-19 0:52 ` SJ Park
2026-09-18 18:16 ` [PATCH 0/3] MAINTAINERS: rework MEMORY MANAGEMENT - MEMORY POLICY AND MIGRATION Joshua Hahn
2026-09-21 7:28 ` Vlastimil Babka (SUSE) [this message]
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=3e9ce58a-1316-48a0-9bab-715c70d117f6@kernel.org \
--to=vbabka@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=matthew.brost@intel.com \
--cc=mhocko@suse.com \
--cc=rakie.kim@sk.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=ying.huang@linux.alibaba.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®