[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220614103842.af0c9a5434e3099cf9060cf5@linux-foundation.org>
Date: Tue, 14 Jun 2022 10:38:42 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Hildenbrand <david@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Oscar Salvador <osalvador@...e.de>
Subject: Re: [PATCH v1] MAINTAINERS: add MEMORY HOT(UN)PLUG section and add
myself as reviewer
On Tue, 14 Jun 2022 08:58:55 +0200 David Hildenbrand <david@...hat.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@...hat.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@...ux-foundation.org>
> > +R: David Hildenbrand <david@...hat.com>
> > +L: linux-mm@...ck.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.
Powered by blists - more mailing lists