From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Shuah Khan <shuah@kernel.org>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: PPC: support kvm selftests
Date: Thu, 16 Mar 2023 22:53:26 +1100 [thread overview]
Message-ID: <87ilf0nc95.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20230316031732.3591455-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> Hi,
>
> This series adds initial KVM selftests support for powerpc
> (64-bit, BookS).
Awesome.
> It spans 3 maintainers but it does not really
> affect arch/powerpc, and it is well contained in selftests
> code, just touches some makefiles and a tiny bit headers so
> conflicts should be unlikely and trivial.
>
> I guess Paolo is the best point to merge these, if no comments
> or objections?
Yeah. If it helps:
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kselftest@vger.kernel.org,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH 0/2] KVM: PPC: support kvm selftests
Date: Thu, 16 Mar 2023 22:53:26 +1100 [thread overview]
Message-ID: <87ilf0nc95.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20230316031732.3591455-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> Hi,
>
> This series adds initial KVM selftests support for powerpc
> (64-bit, BookS).
Awesome.
> It spans 3 maintainers but it does not really
> affect arch/powerpc, and it is well contained in selftests
> code, just touches some makefiles and a tiny bit headers so
> conflicts should be unlikely and trivial.
>
> I guess Paolo is the best point to merge these, if no comments
> or objections?
Yeah. If it helps:
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
cheers
next prev parent reply other threads:[~2023-03-16 11:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 3:17 [PATCH 0/2] KVM: PPC: support kvm selftests Nicholas Piggin
2023-03-16 3:17 ` Nicholas Piggin
2023-03-16 3:17 ` [PATCH 1/2] KVM: PPC: Add kvm selftests support for powerpc Nicholas Piggin
2023-03-16 3:17 ` Nicholas Piggin
2023-03-29 20:19 ` Sean Christopherson
2023-03-29 20:19 ` Sean Christopherson
2023-04-02 0:48 ` Nicholas Piggin
2023-04-02 0:48 ` Nicholas Piggin
2023-03-16 3:17 ` [PATCH 2/2] KVM: PPC: Add basic framework tests for kvm selftests Nicholas Piggin
2023-03-16 3:17 ` Nicholas Piggin
2023-03-16 11:53 ` Michael Ellerman [this message]
2023-03-16 11:53 ` [PATCH 0/2] KVM: PPC: support " Michael Ellerman
2023-03-22 17:41 ` Sean Christopherson
2023-03-22 17:41 ` Sean Christopherson
2023-03-27 5:37 ` Nicholas Piggin
2023-03-27 5:37 ` Nicholas Piggin
2023-03-27 17:43 ` Sean Christopherson
2023-03-27 17:43 ` Sean Christopherson
2023-03-28 6:49 ` Nicholas Piggin
2023-03-28 6:49 ` Nicholas Piggin
2023-03-28 9:07 ` Michael Ellerman
2023-03-28 9:07 ` 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=87ilf0nc95.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.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.