linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul@sk.com>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	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>,
	Joshua Hahn <joshua.hahnjy@gmail.com>,
	Rakie Kim <rakie.kim@sk.com>,
	byungchul.park@sk.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, kernel_team@skhynix.com
Subject: Re: [RFC PATCH] MAINTAINERS: add mm memory policy section
Date: Wed, 14 May 2025 11:42:40 +0900	[thread overview]
Message-ID: <20250514024240.GA39248@system.software.com> (raw)
In-Reply-To: <aCQBJEDWBhFsc7O-@harry>

On Wed, May 14, 2025 at 11:34:12AM +0900, Harry Yoo wrote:
> On Tue, May 13, 2025 at 05:00:07PM +0100, Lorenzo Stoakes 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>
> > +R:	Rakie Kim <rakie.kim@sk.com>
> 
> Maybe
> 
> R: Byungchul Park <byungchul@sk.com> ?
> 
> Although his LUF work hasn't made it upstream, he has a solid understanding
> of migration and it would be helpful to have him involved as a reviewer.
> 
> Of course, only if he has interests and the capacity to review.
> 
> Byungchul, what do you think?

Grateful.  I'd like to contribute as a reviewer on it.

Thanks.

	Byungchul

> > +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
> 
> -- 
> Cheers,
> Harry / Hyeonggon

  reply	other threads:[~2025-05-14  2:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 16:00 [RFC PATCH] MAINTAINERS: add mm memory policy section 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
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 [this message]
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=20250514024240.GA39248@system.software.com \
    --to=byungchul@sk.com \
    --cc=akpm@linux-foundation.org \
    --cc=apopple@nvidia.com \
    --cc=byungchul.park@sk.com \
    --cc=david@redhat.com \
    --cc=harry.yoo@oracle.com \
    --cc=joshua.hahnjy@gmail.com \
    --cc=kernel_team@skhynix.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;
as well as URLs for NNTP newsgroup(s).