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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 14 Jun 2022 11:35:28 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v1] MAINTAINERS: add MEMORY HOT(UN)PLUG section and add
 myself as reviewer

On 14.06.22 11:33, Greg Kroah-Hartman wrote:
> 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@...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/
> 
> Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
> One question, will patches from you go through my driver core tree, or
> the -mm tree?  Either is fine for me, just curious.

In the past, most stuff regarding drivers/base/memory.c went through
-mm, so I'd say we keep it like that, unless it's really generic changes
to the driver model etc.

-- 
Thanks,

David / dhildenb