From: Joshua Hahn <joshua.hahnjy@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>, Zi Yan <ziy@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
Matthew Brost <matthew.brost@intel.com>,
Rakie Kim <rakie.kim@sk.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add mm memory policy section
Date: Tue, 13 May 2025 10:44:49 -0700 [thread overview]
Message-ID: <20250513174453.4153130-1-joshua.hahnjy@gmail.com> (raw)
In-Reply-To: <20250513160007.132378-1-lorenzo.stoakes@oracle.com>
On Tue, 13 May 2025 17:00:07 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
> As part of the ongoing efforts to sub-divide memory management
> maintainership and reviewership, establish a section for memory policy and
> migration and add appropriate maintainers and reviewers.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
>
> REVIEWERS NOTES:
>
> I took a look through git blame, past commits, etc. and came up with what
> seems to be a reasonable list of people here, if you don't feel you ought
> to be here, or if you feel anybody is missing (including yourself!) let me
> know :)
>
> David has kindly already agreed to be co-maintainer for this section.
>
> MAINTAINERS | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 80aa09f2e735..29d73593038c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15567,6 +15567,24 @@ W: http://www.linux-mm.org
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> F: mm/gup.c
>
> +MEMORY MANAGEMENT - MEMORY POLICY AND MIGRATION
> +M: Andrew Morton <akpm@linux-foundation.org>
> +M: David Hildenbrand <david@redhat.com>
> +R: Zi Yan <ziy@nvidia.com>
> +R: Alistair Popple <apopple@nvidia.com>
> +R: Matthew Brost <matthew.brost@intel.com>
> +R: Joshua Hahn <joshua.hahnjy@gmail.com>
Will do my best to review, thank you!
Reviewed-by: Joshua Hahn <joshua.hahnjy@gmail.com>
> +R: Rakie Kim <rakie.kim@sk.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: include/linux/mempolicy.h
> +F: include/linux/migrate.h
> +F: mm/mempolicy.c
> +F: mm/migrate.c
> +F: mm/migrate_device.c
> +
> MEMORY MANAGEMENT - NUMA MEMBLOCKS AND NUMA EMULATION
> M: Andrew Morton <akpm@linux-foundation.org>
> M: Mike Rapoport <rppt@kernel.org>
> --
> 2.49.0
next prev parent reply other threads:[~2025-05-13 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:00 Lorenzo Stoakes
2025-05-13 16:06 ` Zi Yan
2025-05-14 1:52 ` Huang, Ying
2025-05-13 16:21 ` Gregory Price
2025-05-13 18:12 ` Lorenzo Stoakes
2025-05-13 17:03 ` David Hildenbrand
2025-05-13 17:44 ` Joshua Hahn [this message]
2025-05-13 18:16 ` Matthew Brost
2025-05-14 2:03 ` Rakie Kim
2025-05-14 2:34 ` Harry Yoo
2025-05-14 2:42 ` Byungchul Park
2025-05-29 5:54 ` Alistair Popple
2025-05-29 12:14 ` Lorenzo Stoakes
2025-05-30 1:50 ` Alistair Popple
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=20250513174453.4153130-1-joshua.hahnjy@gmail.com \
--to=joshua.hahnjy@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.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