mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v1] MAINTAINERS: add MEMORY HOT(UN)PLUG section and add myself as reviewer
Date: Tue, 14 Jun 2022 10:38:42 -0700	[thread overview]
Message-ID: <20220614103842.af0c9a5434e3099cf9060cf5@linux-foundation.org> (raw)
In-Reply-To: <72194595-a177-088d-28a9-0a24d4192777@redhat.com>

On Tue, 14 Jun 2022 08:58:55 +0200 David Hildenbrand <david@redhat.com> wrote:

> On 10.06.22 12:12, David Hildenbrand wrote:
> > There are certainly a lot more files that partially fall into the memory
> > hot(un)plug category, including parts of mm/sparse.c, mm/page_isolation.c
> > and mm/page_alloc.c. Let's only add what's almost completely memory
> > hot(un)plug related.
> > 
> > Add myself as reviewer so it's easier for contributors to figure out
> > whom to CC.
> > 
> > Signed-off-by: David Hildenbrand <david@redhat.com>
> > ---
> >  MAINTAINERS | 12 ++++++++++++
> >  1 file changed, 12 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index a6d3bd9d2a8d..77aebce76288 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -12848,6 +12848,18 @@ F:	include/linux/vmalloc.h
> >  F:	mm/
> >  F:	tools/testing/selftests/vm/
> >  
> > +MEMORY HOT(UN)PLUG
> > +M:	Andrew Morton <akpm@linux-foundation.org>
> > +R:	David Hildenbrand <david@redhat.com>
> > +L:	linux-mm@kvack.org
> > +S:	Maintained
> > +F:	Documentation/admin-guide/mm/memory-hotplug.rst
> > +F:	Documentation/core-api/memory-hotplug.rst
> > +F:	drivers/base/memory.c
> > +F:	include/linux/memory_hotplug.h
> > +F:	mm/memory_hotplug.c
> > +F:	tools/testing/selftests/memory-hotplug/
> 
> (thanks for the kind words from reviewers :) )
> 
> Thinking about it (and remembering having a discussion about
> submaintainers for MM in general at LSF/MM):
> 
> @Andrew, do we want "official" submaintainers for that section? If so,
> we could turn my R into an M. Further, Oscar did a lot of work in the
> memory hot(un)plug world as well -- so if we want submaintainers, Oscar
> might be a very good fit as well.
> 
> ... I guess, that would mostly reflect reality :)

um, fine, no opinion really.  I think the main thing is to make
get_maintainer.pl spit out all the suitable email addresses.

  parent reply	other threads:[~2022-06-14 17:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 10:12 David Hildenbrand
2022-06-11  2:02 ` Miaohe Lin
2022-06-11 13:11 ` Muchun Song
2022-06-14  6:58 ` David Hildenbrand
2022-06-14  7:36   ` Oscar Salvador
2022-06-14 17:38   ` Andrew Morton [this message]
2022-06-15  4:03     ` Oscar Salvador
2022-06-15  9:15       ` David Hildenbrand
2022-06-15 21:28         ` Andrew Morton
2022-06-14  9:33 ` Greg Kroah-Hartman
2022-06-14  9:35   ` David Hildenbrand
2022-06-14 10:26     ` Greg Kroah-Hartman

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=20220614103842.af0c9a5434e3099cf9060cf5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=osalvador@suse.de \
    /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®