From: John Hubbard <jhubbard@nvidia.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>, Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add mm GUP section
Date: Tue, 6 May 2025 10:41:06 -0700 [thread overview]
Message-ID: <adda523d-83a5-4a59-8132-57be56b3d6d6@nvidia.com> (raw)
In-Reply-To: <20250506173601.97562-1-lorenzo.stoakes@oracle.com>
On 5/6/25 10:36 AM, Lorenzo Stoakes wrote:
> As part of the ongoing efforts to sub-divide memory management
> maintainership and reviewership, establish a section for GUP (Get User
> Pages) support and add appropriate maintainers and reviewers.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> MAINTAINERS | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
thanks,
--
John Hubbard
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d274e6802ba5..9c769f7d135b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15540,6 +15540,18 @@ S: Maintained
> F: include/linux/execmem.h
> F: mm/execmem.c
>
> +MEMORY MANAGEMENT - GUP (GET USER PAGES)
> +M: Andrew Morton <akpm@linux-foundation.org>
> +M: David Hildenbrand <david@redhat.com>
> +R: Jason Gunthorpe <jgg@nvidia.com>
> +R: John Hubbard <jhubbard@nvidia.com>
> +R: Peter Xu <peterx@redhat.com>
> +L: linux-mm@kvack.org
> +S: Maintained
> +W: http://www.linux-mm.org
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> +F: mm/gup.c
> +
> MEMORY MANAGEMENT - NUMA MEMBLOCKS AND NUMA EMULATION
> M: Andrew Morton <akpm@linux-foundation.org>
> M: Mike Rapoport <rppt@kernel.org>
next prev parent reply other threads:[~2025-05-06 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:36 Lorenzo Stoakes
2025-05-06 17:41 ` John Hubbard [this message]
2025-05-06 23:21 ` Andrew Morton
2025-05-07 8:05 ` David Hildenbrand
2025-05-07 9:02 ` Uladzislau Rezki
2025-05-07 9:23 ` Lorenzo Stoakes
2025-05-07 9:59 ` Uladzislau Rezki
2025-05-08 8:53 ` David Hildenbrand
2025-05-08 12:23 ` Lorenzo Stoakes
[not found] ` <6050270f-1556-4df3-beab-63e907b28d82@lucifer.local>
2025-05-08 17:43 ` David Hildenbrand
2025-05-08 18:50 ` Lorenzo Stoakes
2025-05-12 7:38 ` Vlastimil Babka
2025-05-12 12:54 ` Zi Yan
2025-05-12 13:01 ` David Hildenbrand
2025-05-12 13:10 ` Lorenzo Stoakes
2025-05-12 13:06 ` Lorenzo Stoakes
2025-05-13 6:23 ` Mike Rapoport
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=adda523d-83a5-4a59-8132-57be56b3d6d6@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=peterx@redhat.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