linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Harry Yoo <harry.yoo@oracle.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Rik van Riel <riel@surriel.com>, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] MAINTAINERS: add reverse mapping section
Date: Thu, 17 Apr 2025 10:53:33 +0200	[thread overview]
Message-ID: <eb71267a-80ce-49f9-a475-5260df607458@redhat.com> (raw)
In-Reply-To: <20250417084904.16806-1-lorenzo.stoakes@oracle.com>

On 17.04.25 10:49, Lorenzo Stoakes wrote:
> Separate out the reverse mapping part of memory management and assign
> appropriate maintainers and reviewers.
> 
> David has long been invovled in work with the reverse mapping and continues
> to do so, so is well suited to maintain this area of the kernel.
> 
> I have a lot of experience working with the anonymous reverse mapping and
> continue to work in this area, and also have good knowledge of the walking
> code and code related to VMAs.
> 
> This helps people identify who to ask for help, and also additionally makes
> life easier in review.
> 
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
>   MAINTAINERS | 13 ++++++++++++-
>   1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8d834514a047..4f6d09c3fd9d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15499,7 +15499,6 @@ F:	include/linux/mm_*.h
>   F:	include/linux/mmzone.h
>   F:	include/linux/mmu_notifier.h
>   F:	include/linux/pagewalk.h
> -F:	include/linux/rmap.h
>   F:	include/trace/events/ksm.h
>   F:	mm/
>   F:	tools/mm/
> @@ -15539,6 +15538,18 @@ F:	mm/page_alloc.c
>   F:	include/linux/gfp.h
>   F:	include/linux/compaction.h
> 
> +MEMORY MANAGEMENT - RMAP (REVERSE MAPPING)
> +M:	Andrew Morton <akpm@linux-foundation.org>
> +M:	David Hildenbrand <david@redhat.com>
> +M:	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> +R:	Liam R. Howlett <Liam.Howlett@oracle.com>
> +R:	Vlastimil Babka <vbabka@suse.cz>
> +R:	Harry Yoo <harry.yoo@oracle.com>
> +L:	linux-mm@kvack.org
> +S:	Maintained
> +F:	include/linux/rmap.h
> +F:	mm/rmap.c
> +
>   MEMORY MANAGEMENT - SECRETMEM
>   M:	Andrew Morton <akpm@linux-foundation.org>
>   M:	Mike Rapoport <rppt@kernel.org>
> --
> 2.49.0
> 

Acked-by: David Hildenbrand <david@redhat.com>

Let me CC Rik and Hugh, if they also have interest + capacity.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2025-04-17  8:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  8:49 Lorenzo Stoakes
2025-04-17  8:53 ` David Hildenbrand [this message]
2025-04-17  9:03   ` Lorenzo Stoakes
2025-04-17  9:05   ` Hugh Dickins
2025-04-17 18:06   ` Rik van Riel
2025-04-17 18:16     ` Lorenzo Stoakes
2025-04-17  9:28 ` Vlastimil Babka
2025-04-17 14:41 ` Harry Yoo
2025-04-17 17:14 ` Liam R. Howlett

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=eb71267a-80ce-49f9-a475-5260df607458@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=harry.yoo@oracle.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=riel@surriel.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