From: Sean Christopherson <seanjc@google.com>
To: Like Xu <like.xu.linux@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: selftests: Report enable_pmu module value when test is skipped
Date: Fri, 24 Mar 2023 14:25:26 -0700 [thread overview]
Message-ID: <ZB4VRvjUP75kpw71@google.com> (raw)
In-Reply-To: <167969136143.2756283.9405259236021680651.b4-ty@google.com>
On Fri, Mar 24, 2023, Sean Christopherson wrote:
> On Tue, 14 Feb 2023 16:49:18 +0800, Like Xu wrote:
> > Adequate info can help developers quickly distinguish whether the cause
> > is a code flaw or a platform limitation when a test fails or is skipped,
> > and this minor patch-set is doing a little work in that direction.
> >
> > Base: kvm-x86/next
> >
> > Like Xu (2):
> > KVM: selftests: Add a helper to read kvm boolean module parameters
> > KVM: selftests: Report enable_pmu module value when test is skipped
> >
> > [...]
>
> Applied to kvm-x86 selftests, thanks!
>
> [1/2] KVM: selftests: Add a helper to read kvm boolean module parameters
> https://github.com/kvm-x86/linux/commit/d14d9139c023
> [2/2] KVM: selftests: Report enable_pmu module value when test is skipped
> https://github.com/kvm-x86/linux/commit/6cf332e8eca6
Replaced patch 2 with your v2:
KVM: selftests: Report enable_pmu module value when test is skipped
https://github.com/kvm-x86/linux/commit/5b1abc285a08
prev parent reply other threads:[~2023-03-24 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 8:49 [PATCH 0/2] KVM: selftests: Report enable_pmu module value when test is skipped Like Xu
2023-02-14 8:49 ` [PATCH 1/2] KVM: selftests: Add a helper to read kvm boolean module parameters Like Xu
2023-02-14 8:49 ` [PATCH 2/2] KVM: selftests: Report enable_pmu module value when test is skipped Like Xu
2023-02-14 18:03 ` Sean Christopherson
2023-03-24 20:58 ` [PATCH 0/2] " Sean Christopherson
2023-03-24 21:25 ` Sean Christopherson [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=ZB4VRvjUP75kpw71@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).