From: Marc Zyngier <maz@kernel.org>
To: Ricardo Koller <ricarkol@google.com>
Cc: Sean Christopherson <seanjc@google.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
pbonzini@redhat.com, drjones@redhat.com, eric.auger@redhat.com,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] KVM: selftests: Rename vm_handle_exception in evmcs test
Date: Mon, 07 Jun 2021 18:18:41 +0100 [thread overview]
Message-ID: <87im2pzj7y.wl-maz@kernel.org> (raw)
In-Reply-To: <YL5P28rvUcM3ohxx@google.com>
On Mon, 07 Jun 2021 17:56:59 +0100,
Ricardo Koller <ricarkol@google.com> wrote:
>
> On Mon, Jun 07, 2021 at 05:19:03PM +0100, Marc Zyngier wrote:
> > On Mon, 07 Jun 2021 17:07:40 +0100,
> > Sean Christopherson <seanjc@google.com> wrote:
> > >
> > > On Sun, Jun 06, 2021, Marc Zyngier wrote:
> > > > This is becoming a bit messy. I'd rather drop the whole series from
> > > > -next, and get something that doesn't break in the middle. Please
> > > > resend the series tested on top of -rc4.
> > >
> > > That'd be my preference too. I almost asked if it could be (temporarily)
> > > dropped, but I assumed the hashes in -next are intended to be stable.
> >
> > I usually try and keep these commits stable.
> >
> > But in this case, we end-up with a broken build at some point in the
> > series. For such cases, I'm more than happy to drop the series and
> > merge a clean version again (I keep each series on a separate branch
> > for this exact purpose).
>
> Thank you both. I will send a new series with the fix and Seans
> suggestions (tested on the latest rc).
>
> Apologies again for the mess.
No worries, that's a pretty common situation.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-06-07 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 18:18 [PATCH] KVM: selftests: Rename vm_handle_exception in evmcs test Ricardo Koller
2021-06-04 21:26 ` Sean Christopherson
2021-06-04 23:11 ` Ricardo Koller
2021-06-06 10:10 ` Marc Zyngier
2021-06-07 16:07 ` Sean Christopherson
2021-06-07 16:19 ` Marc Zyngier
2021-06-07 16:56 ` Ricardo Koller
2021-06-07 17:18 ` Marc Zyngier [this message]
2021-06-08 22:11 ` Ricardo Koller
2021-06-09 16:34 ` Sean Christopherson
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=87im2pzj7y.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=oliver.sang@intel.com \
--cc=pbonzini@redhat.com \
--cc=ricarkol@google.com \
--cc=seanjc@google.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).