linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Oscar Salvador <osalvador@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1] MAINTAINERS: add MEMORY HOT(UN)PLUG section and add myself as reviewer
Date: Wed, 15 Jun 2022 11:15:30 +0200	[thread overview]
Message-ID: <16297304-82d9-f62b-b87f-cc8d8fde9bd4@redhat.com> (raw)
In-Reply-To: <YqlaE/LYHwB0gpaW@localhost.localdomain>

On 15.06.22 06:03, Oscar Salvador wrote:
> On Tue, Jun 14, 2022 at 10:38:42AM -0700, Andrew Morton wrote:
>> On Tue, 14 Jun 2022 08:58:55 +0200 David Hildenbrand <david@redhat.com> wrote:
>> um, fine, no opinion really.  I think the main thing is to make
>> get_maintainer.pl spit out all the suitable email addresses.
> 
> As already pointed out, David and I have already kind of acted as maintainers of
> this aready already for quite some time, reviewing and contributing the most, so
> it might make sense to just spell that out, so, without willing to step on
> anyone's toes, what about this:
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1fc9ead83d2a..f5a746624a9f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -12857,6 +12857,18 @@ F:     include/linux/vmalloc.h
>  F:     mm/
>  F:     tools/testing/selftests/vm/
>  
> +MEMORY HOT(UN)PLUG
> +M:     David Hildenbrand <david@redhat.com>
> +M:     Oscar Salvador <osalvador@suse.de>
> +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/

Fine with me to remove Andrew from that list because he's implicitly
covering most stuff via the "MEMORY MANAGEMENT" section.

@Andrew, whatever you prefer.

Acked-by: David Hildenbrand <david@redhat.com>


@Andrew, would it make sense to update the git tree in the "MEMORY
MANAGEMENT" section now that mm-stable etc. resides on git.kernel.org ?


-- 
Thanks,

David / dhildenb



  reply	other threads:[~2022-06-15  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 10:12 [PATCH v1] MAINTAINERS: add MEMORY HOT(UN)PLUG section and add myself as reviewer 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
2022-06-15  4:03     ` Oscar Salvador
2022-06-15  9:15       ` David Hildenbrand [this message]
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=16297304-82d9-f62b-b87f-cc8d8fde9bd4@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).