From: Bill Wendling <morbo@google.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: kvm list <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>
Subject: Re: [kvm-unit-tests PATCH 1/2] Use a status enum for reporting pass/fail
Date: Mon, 14 Oct 2019 11:23:39 -0700 [thread overview]
Message-ID: <CAGG=3QX-dd3z4FeeFPuT0q43mFRR0nnEf8g7fHbdxWRzDL_YMA@mail.gmail.com> (raw)
In-Reply-To: <20191014162657.GB22962@linux.intel.com>
On Mon, Oct 14, 2019 at 9:27 AM Sean Christopherson
<sean.j.christopherson@intel.com> wrote:
>
> On Sat, Oct 12, 2019 at 12:44:53AM -0700, Bill Wendling wrote:
> > Some values passed into "report" as "pass/fail" are larger than the
> > size of the parameter. Instead use a status enum so that the size of the
> > argument no longer matters.
> >
> > Signed-off-by: Bill Wendling <morbo@google.com>
>
> The threading of these mails has me all kinds of confused. What is the
> relationship between all these patches? Did you perhaps intend to send
> some of these as v2?
>
> [kvm-unit-tests PATCH 1/2] Use a status enum for reporting pass/fail
> [kvm-unit-tests PATCH 2/2] Use a status enum for reporting pass/fail
> [kvm-unit-tests PATCH 1/1] x86: use pointer for end of exception table
> [kvm-unit-tests PATCH 2/2] x86: use pointer for end of exception table
Yes, the later ones are meant as v2. I'm not familiar with the patch
submission policy via emails. :-(
-bw
next prev parent reply other threads:[~2019-10-14 18:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 7:44 [kvm-unit-tests PATCH 1/2] Use a status enum for reporting pass/fail Bill Wendling
2019-10-12 7:44 ` [kvm-unit-tests PATCH 2/2] x86: use pointer for end of exception table Bill Wendling
2019-10-13 7:18 ` [kvm-unit-tests PATCH 1/1] " Bill Wendling
2019-10-15 7:41 ` Thomas Huth
2019-10-15 8:06 ` Bill Wendling
2019-10-12 8:20 ` [kvm-unit-tests PATCH 2/2] Use a status enum for reporting pass/fail Bill Wendling
2019-10-14 16:26 ` [kvm-unit-tests PATCH 1/2] " Sean Christopherson
2019-10-14 18:23 ` Bill Wendling [this message]
2019-10-15 20:46 ` [kvm-unit-tests v2 PATCH 0/2] Clang compilation fixes Bill Wendling
2019-10-15 20:46 ` [kvm-unit-tests v2 PATCH 1/2] lib: use a status enum for reporting pass/fail Bill Wendling
2019-10-15 20:46 ` [kvm-unit-tests v2 PATCH 2/2] x86: don't compare two global objects' addrs for inequality Bill Wendling
2019-10-16 5:53 ` Thomas Huth
2019-10-21 15:33 ` Paolo Bonzini
2019-10-21 15:32 ` [kvm-unit-tests PATCH 1/2] Use a status enum for reporting pass/fail Paolo Bonzini
2019-10-29 18:51 ` Bill Wendling
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='CAGG=3QX-dd3z4FeeFPuT0q43mFRR0nnEf8g7fHbdxWRzDL_YMA@mail.gmail.com' \
--to=morbo@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.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).