From: Yuanchu Xie <yuanchu@google.com>
To: Wei Liu <liuwe@microsoft.com>, Rob Bradford <rbradford@rivosinc.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Dan Williams <dan.j.williams@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux.dev, dev@lists.cloudhypervisor.org,
Yuanchu Xie <yuanchu@google.com>
Subject: [RFC PATCH v1 2/2] virt: memctl: add Yuanchu and Pasha as maintainers
Date: Mon, 13 May 2024 19:03:01 -0700 [thread overview]
Message-ID: <20240514020301.1835794-2-yuanchu@google.com> (raw)
In-Reply-To: <20240514020301.1835794-1-yuanchu@google.com>
The memctl driver lives under drivers/virt/memctl. We specify
maintainers for the driver.
Signed-off-by: Yuanchu Xie <yuanchu@google.com>
---
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 61117c3afa80..5793df2b2f5e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14057,6 +14057,13 @@ F: mm/memblock.c
F: mm/mm_init.c
F: tools/testing/memblock/
+MEMCTL GUEST DRIVER
+M: Yuanchu Xie <yuanchu@google.com>
+M: Pasha Tatashin <pasha.tatashin@soleen.com>
+L: linux-kernel@vger.kernel.org
+S: Supported
+F: drivers/virt/memctl/
+
MEMORY CONTROLLER DRIVERS
M: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
L: linux-kernel@vger.kernel.org
--
2.45.0.rc1.225.g2a3ae87e7f-goog
next prev parent reply other threads:[~2024-05-14 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 2:03 [RFC PATCH v1 1/2] virt: memctl: control guest physical memory properties Yuanchu Xie
2024-05-14 2:03 ` Yuanchu Xie [this message]
2024-05-14 16:06 ` Greg Kroah-Hartman
2024-05-15 1:21 ` Yuanchu Xie
2024-05-15 5:34 ` Greg Kroah-Hartman
2024-05-14 16:07 ` Greg Kroah-Hartman
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=20240514020301.1835794-2-yuanchu@google.com \
--to=yuanchu@google.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dev@lists.cloudhypervisor.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuwe@microsoft.com \
--cc=pasha.tatashin@soleen.com \
--cc=rbradford@rivosinc.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=thomas.lendacky@amd.com \
--cc=tytso@mit.edu \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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