Sean Christopherson writes:
> 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
>> p
On Thu, 08 Jun 2023 12:45:04 +1000, 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,
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 maintai
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 i
Nicholas Piggin 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 wh
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
