linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Update MAINTAINERS
Date: Wed, 28 Jun 2023 10:56:09 -0700	[thread overview]
Message-ID: <ZJx0OVEphb/OqQ+t@google.com> (raw)
In-Reply-To: <20230608024504.58189-1-npiggin@gmail.com>

On Thu, Jun 08, 2023, Nicholas Piggin wrote:
> Michael is merging KVM PPC patches via the powerpc tree and KVM topic
> branches. He doesn't necessarily have time to be across all of KVM so
> is reluctant to call himself maintainer, but for the mechanics of how
> patches flow upstream, it is maintained and does make sense to have
> some contact people in MAINTAINERS.
> 
> So add Michael Ellerman as KVM PPC maintainer and myself as reviewer.
> Split out the subarchs that don't get so much attention.
> 
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---

Thanks for documenting the reality of things, much appreciated!

Acked-by: Sean Christopherson <seanjc@google.com>

>  MAINTAINERS | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0dab9737ec16..44417acd2936 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11379,7 +11379,13 @@ 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)

Do you think there's any chance of dropping support for everything except Book3S
64-bit HV at some point soonish?  There haven't been many generic KVM changes that
touch PPC, but in my experience when such series do come along, the many flavors
and layers of PPC incur quite a bit of development and testing cost, and have a
high chance of being broken compared to other architectures.

  reply	other threads:[~2023-06-28 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  2:45 [PATCH] KVM: PPC: Update MAINTAINERS Nicholas Piggin
2023-06-28 17:56 ` Sean Christopherson [this message]
2023-07-05 10:24   ` Michael Ellerman
2023-07-03  5:26 ` 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=ZJx0OVEphb/OqQ+t@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).