mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"KVM list" <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM changes for 4.16-rc3
Date: Mon, 26 Feb 2018 09:28:27 +0100	[thread overview]
Message-ID: <30581e0c-88f0-8a8e-a620-e5b20027175b@redhat.com> (raw)
In-Reply-To: <CA+55aFxeFRsDB+DaDW+E1daFRgk4Ccy=Tmt7cPn2A-uCmqW1iw@mail.gmail.com>

On 25/02/2018 01:05, Linus Torvalds wrote:
> On Fri, Feb 23, 2018 at 5:46 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> This has 28 fixes that were committed one hour before you sent this email.
> 
> I pulled, but I think I'm going to unpull, just because I want an
> explanation of how that could possibly have had sufficient testing for
> the upcoming rc?

I rebased to correct a "Fixes" tag that pointed to the wrong commit.
This: https://marc.info/?l=kvm&m=151943277910352&w=2 is the mail that
pointed out the right commit, and you can see that those 28 commits have
times that are clustered five minutes after that mail.

The SEV patches indeed have been committed about half an hour before
sending the PULL request, because no one outside AMD has all the
hardware and code to test them.  Half an hour is about the time it takes
me to do the final smoke test before sending a pull request.

Paolo

  reply	other threads:[~2018-02-26  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24  1:46 Paolo Bonzini
2018-02-25  0:05 ` Linus Torvalds
2018-02-26  8:28   ` Paolo Bonzini [this message]
2018-02-26 16:13     ` Linus Torvalds

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=30581e0c-88f0-8a8e-a620-e5b20027175b@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®