From: Mike Rapoport <rppt@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] MAINTAINERS: rename MM to MM MISC, add missing files
Date: Wed, 23 Jul 2025 08:18:34 +0300 [thread overview]
Message-ID: <aIBwqmITl1VyZp7S@kernel.org> (raw)
In-Reply-To: <20250722192704.164758-1-lorenzo.stoakes@oracle.com>
On Tue, Jul 22, 2025 at 08:27:04PM +0100, Lorenzo Stoakes wrote:
> To fit in with other sections within MAINTAINERS for memory management
> files, rename the MEMORY MANAGEMENT section to MEMORY MANAGEMENT - MISC to
> contain files that are not described by other sections.
>
> We also add missing files to MEMORY MANAGEMENT - MISC and MEMORY MANAGEMENT
> - CORE sections.
>
> Move over appropriate files to the core section, and in both sections add
> remaining missing files. At this point, with the other recent MAINTAINERS
> changes, this should now mean that every memory management-related file has
> a section and assigned maintainers/reviewers.
>
> For the time being, we maintain catch-all mm/ and tools/mm/ entries for MM
> - MISC, though in future we may wish to remove these to make it obvious
> when files don't have assigned entries.
>
> Finally, we copy across the maintainers/reviewers from MEMORY MANAGEMENT -
> CORE to MEMORY MANAGEMENT - MISC, as it seems the two are sufficiently
> related for this to be sensible.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-07-23 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 19:27 [PATCH] MAINTAINERS: rename MM to MM MISC, add missing files Lorenzo Stoakes
2025-07-23 5:18 ` Mike Rapoport [this message]
2025-07-23 9:42 ` Vlastimil Babka
2025-07-23 9:46 ` Lorenzo Stoakes
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=aIBwqmITl1VyZp7S@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).