From: David Hildenbrand <david@redhat.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add further core files to mm core section
Date: Tue, 17 Jun 2025 09:59:01 +0200 [thread overview]
Message-ID: <4b0036ae-5b92-49b5-8396-412c7026b105@redhat.com> (raw)
In-Reply-To: <aFDm0YrbSAvXc5Wp@kernel.org>
On 17.06.25 05:53, Mike Rapoport wrote:
> On Mon, Jun 16, 2025 at 11:10:41PM +0200, David Hildenbrand wrote:
>> On 16.06.25 22:38, Lorenzo Stoakes wrote:
>>> There are a number of files which don't quite belong anywhere else, so
>>> place them in the core section. If we determine in future they belong
>>> elsewhere we can update incrementally but it is preferable that we assign
>>> each file to a section as best we can.
>>>
>>> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>>> ---
>>> REVIEWERS - let me know if these seem appropriate, I'm eyeballing
>>> this. even if they are not quite best placed a 'best effort' is still
>>> worthwhile so we establish a place to put all mm files, we can always
>>> incrementally update these later.
>>>
>>> MAINTAINERS | 28 ++++++++++++++++++++++++----
>>> 1 file changed, 24 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 4523a6409186..a61d56bd7aa4 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -15740,10 +15740,6 @@ F: include/linux/memory_hotplug.h
>>> F: include/linux/memory-tiers.h
>>> F: include/linux/mempolicy.h
>>> F: include/linux/mempool.h
>>> -F: include/linux/memremap.h
>>> -F: include/linux/mmzone.h
>>> -F: include/linux/mmu_notifier.h
>>> -F: include/linux/pagewalk.h
>>> F: include/trace/events/ksm.h
>>> F: mm/
>>> F: tools/mm/
>>
>> Probably better to have some section than none ... was just briefly
>> wondering if "CORE" is the right section for some of that. Some of that
>> might be better of in a "MM MISC" section, maybe.
>
> Maybe rather than add files to MM CORE we should move mm/ there and add the
> MM MISC section for files we explicitly want to exclude from MM CORE?
Also an option, yes,
>
>>> @@ -15764,16 +15760,40 @@ S: Maintained
>>> W: http://www.linux-mm.org
>>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>>> F: include/linux/memory.h
>>> +F: include/linux/memremap.h
>>> F: include/linux/mm.h
>>> F: include/linux/mm_*.h
>>> F: include/linux/mmdebug.h
>>> +F: include/linux/mmu_notifier.h
>>> +F: include/linux/mmzone.h
>>> F: include/linux/pagewalk.h
>>> F: kernel/fork.c
>>> F: mm/Kconfig
>>> F: mm/debug.c
>>> +F: mm/debug_page_ref.c
>>> +F: mm/debug_vm_pgtable.c
>>
>> Wondering if there should be a MM DEBUG section. But then, no idea who in
>> their right mind would be willing to maintain that ;)
>
> The same people that maintain MM CORE? ;-)
Heh :P
>
>>> +F: mm/folio-compat.c
>>> +F: mm/highmem.c
>>> F: mm/init-mm.c
>>> +F: mm/internal.h
>>> +F: mm/interval_tree.c
>
> Looks like VMA to me.
It's more about anon_vma I guess, so rmap ... maybe.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-06-17 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:38 Lorenzo Stoakes
2025-06-16 21:10 ` David Hildenbrand
2025-06-16 22:56 ` Shakeel Butt
2025-06-17 15:22 ` Lorenzo Stoakes
2025-06-17 17:51 ` Shakeel Butt
2025-06-17 17:55 ` Lorenzo Stoakes
2025-06-17 3:53 ` Mike Rapoport
2025-06-17 7:59 ` David Hildenbrand [this message]
2025-06-17 15:04 ` Lorenzo Stoakes
2025-06-17 15:46 ` David Hildenbrand
2025-07-22 13:53 ` Lorenzo Stoakes
2025-07-22 14:22 ` Vlastimil Babka
2025-07-23 5:36 ` Christoph Hellwig
2025-06-17 15:26 ` Lorenzo Stoakes
2025-06-19 5:31 ` Alistair Popple
2025-06-17 18:47 ` Vlastimil Babka
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=4b0036ae-5b92-49b5-8396-412c7026b105@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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