From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [RFC PATCH] KVM: PPC: Update MAINTAINERS
Date: Sat, 8 Apr 2023 14:28:39 +1000 [thread overview]
Message-ID: <20230408042839.869361-1-npiggin@gmail.com> (raw)
Michael is maintaining KVM PPC with the powerpc tree at the moment,
just doesn't necessarily have time to be across all of KVM. But I
think that's okay, from mechanics of how patches flow upstream he is
maintainer. And it probably makes a bit more sense to people who need
to look at the MAINTAINERS file if we have some contacts there.
So add mpe as KVM PPC maintainer and I am a reviewer. Split out the
subarchs that don't get much attention.
Thanks,
Nick
---
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 90abe83c02f3..c6283280683e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11292,8 +11292,15 @@ F: arch/mips/include/uapi/asm/kvm*
F: arch/mips/kvm/
KERNEL VIRTUAL MACHINE FOR POWERPC (KVM/powerpc)
+M: Michael Ellerman <mpe@ellerman.id.au>
+R: Nicholas Piggin <npiggin@gmail.com>
L: linuxppc-dev@lists.ozlabs.org
+L: kvm@vger.kernel.org
+S: Maintained (Book3S 64-bit HV)
+S: Odd fixes (Book3S 64-bit PR)
+S: Orphan (Book3E and 32-bit)
T: git git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git topic/ppc-kvm
+S: Maintained
F: arch/powerpc/include/asm/kvm*
F: arch/powerpc/include/uapi/asm/kvm*
F: arch/powerpc/kernel/kvm*
--
2.40.0
next reply other threads:[~2023-04-08 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 4:28 Nicholas Piggin [this message]
2023-04-20 14:05 ` [RFC PATCH] KVM: PPC: Update MAINTAINERS Michael Ellerman
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=20230408042839.869361-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.