From: Vlastimil Babka <vbabka@suse.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v2] MAINTAINERS: add MM MISC section, add missing files to MISC and CORE
Date: Wed, 23 Jul 2025 17:32:57 +0200 [thread overview]
Message-ID: <7b8ec9ae-3eaf-4e66-b903-ba3c7f9a20be@suse.cz> (raw)
In-Reply-To: <20250723095823.21940-1-lorenzo.stoakes@oracle.com>
On 7/23/25 11:58, Lorenzo Stoakes wrote:
> Add a MEMORY MANAGEMENT - MISC section to contain files that are not described
> by other sections, moving all but the catch-all mm/ and tools/mm/ from MEMORY
> MANAGEMENT to MEMORY MANAGEMENT - CORE and MEMORY MANAGEMENT - MISC as
> appropriate.
>
> 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.
>
> 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>
Acked-by: Vlastimil Babka <vbabka@suse.cZ>
prev parent reply other threads:[~2025-07-23 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 9:58 Lorenzo Stoakes
2025-07-23 10:36 ` David Hildenbrand
2025-07-23 10:50 ` Lorenzo Stoakes
2025-07-23 10:42 ` David Hildenbrand
2025-07-23 15:05 ` Lorenzo Stoakes
2025-07-23 15:13 ` Vlastimil Babka
2025-07-23 15:20 ` Lorenzo Stoakes
2025-07-23 15:32 ` Vlastimil Babka [this message]
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=7b8ec9ae-3eaf-4e66-b903-ba3c7f9a20be@suse.cz \
--to=vbabka@suse.cz \
--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=rppt@kernel.org \
--cc=surenb@google.com \
/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