From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Michal Hocko <mhocko@kernel.org>, Mike Rapoport <rppt@kernel.org>,
Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] MAINTAINERS: add my isub-entries to MM part.
Date: Wed, 26 Mar 2025 23:55:37 +0200 [thread overview]
Message-ID: <20250326215541.1809379-1-rppt@kernel.org> (raw)
From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Following discussion at LSF/MM/BPF I'm adding execmem, secretmem and
numa memblocks sub-entries for MEMORY MANAGEMENT in MAINTAINERS.
The changes for USERFAULTFD entry are fixups that can be folded into the
original patch if Peter does not mind.
Mike Rapoport (Microsoft) (4):
MAINTAINERS: fixup USERFAULTFD entry
MAINTAINERS: mm: add entry for execmem
MAINTAINERS: mm: add entry for numa memblocks and numa emulation
MAINTAINERS: mm: add entry for secretmem
MAINTAINERS | 50 +++++++++++++++++++++++++++++++++++++++-----------
1 file changed, 39 insertions(+), 11 deletions(-)
base-commit: 87f556baedc9cca2edb318efe9d8cf009d916c4d
--
2.47.2
next reply other threads:[~2025-03-26 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 21:55 Mike Rapoport [this message]
2025-03-26 21:55 ` [PATCH 1/4] MAINTAINERS: fixup USERFAULTFD entry Mike Rapoport
2025-03-26 21:55 ` [PATCH 2/4] MAINTAINERS: mm: add entry for execmem Mike Rapoport
2025-03-26 21:55 ` [PATCH 3/4] MAINTAINERS: mm: add entry for numa memblocks and numa emulation Mike Rapoport
2025-03-26 21:55 ` [PATCH 4/4] MAINTAINERS: mm: add entry for secretmem Mike Rapoport
2025-03-27 13:33 ` [PATCH 0/4] MAINTAINERS: add my isub-entries to MM part Michal Hocko
2025-03-28 13:01 ` Oscar Salvador
2025-03-29 20:46 ` Vlastimil Babka
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=20250326215541.1809379-1-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.