From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: peterx@redhat.com, Axel Rasmussen <axelrasmussen@google.com>,
Mike Rapoport <rppt@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Lorenzo Stoakes <lstoakes@gmail.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] MAINTAINERS: Add myself as userfaultfd reviewer
Date: Fri, 21 Mar 2025 20:21:24 -0400 [thread overview]
Message-ID: <20250322002124.131736-1-peterx@redhat.com> (raw)
Add an entry for userfaultfd and make myself a reviewer of it, just in case
it helps people manage the cc list.
I named it MEMORY USERFAULTFD, could be a bad name, but then it can be
together with the MEMORY* entries when everything is in alphabetic order,
which is definitely a benefit.
The line may not change much on how I'd work with userfaultfd; I think I'll
do the same as before.. But maybe it still, more or less, adds some
responsibility on top, indeed.
Cc: Andrea Arcangeli <aarcange@redhat.com>
Suggested-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Peter Xu <peterx@redhat.com>
---
MAINTAINERS | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e714ea3a7c9f..844e3e1e05d2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15220,6 +15220,17 @@ F: mm/vma.h
F: mm/vma_internal.h
F: tools/testing/vma/
+MEMORY USERFAULTFD
+M: Andrew Morton <akpm@linux-foundation.org>
+R: Peter Xu <peterx@redhat.com>
+S: Maintained
+F: mm/userfaultfd.c
+F: fs/userfaultfd.c
+F: include/uapi/linux/userfaultfd.h
+F: include/asm-generic/pgtable_uffd.h
+F: Documentation/admin-guide/mm/userfaultfd.rst
+F: tools/testing/selftests/mm/uffd-*.[ch]
+
MEMORY TECHNOLOGY DEVICES (MTD)
M: Miquel Raynal <miquel.raynal@bootlin.com>
M: Richard Weinberger <richard@nod.at>
--
2.48.1
next reply other threads:[~2025-03-22 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 0:21 Peter Xu [this message]
2025-03-22 0:53 ` Andrew Morton
2025-03-22 13:14 ` Mike Rapoport
2025-03-25 18:41 ` Liam R. Howlett
2025-03-28 16:10 ` 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=20250322002124.131736-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=rppt@kernel.org \
/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