Re: [PATCH v1] MAINTAINERS: add MEMORY HOT(UN)PLUG section and add myself as reviewer

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Fri, Jun 10, 2022 at 12:12:58PM +0200, 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/

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

One question, will patches from you go through my driver core tree, or
the -mm tree?  Either is fine for me, just curious.

thanks,

greg k-h