From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [RFC PATCH] KVM: PPC: Update MAINTAINERS
Date: Fri, 21 Apr 2023 00:05:33 +1000 [thread overview]
Message-ID: <87jzy64pjm.fsf@mail.concordia> (raw)
In-Reply-To: <20230408042839.869361-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> 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.
Yeah I guess this is better than what we have now.
Can you send a non-RFC and SOB'ed version, and maybe Cc the KVM list
as well?
cheers
prev parent reply other threads:[~2023-04-20 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 4:28 [RFC PATCH] KVM: PPC: Update MAINTAINERS Nicholas Piggin
2023-04-20 14:05 ` Michael Ellerman [this message]
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=87jzy64pjm.fsf@mail.concordia \
--to=mpe@ellerman.id.au \
--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).