From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Nathan Chancellor" <natechancellor@gmail.com>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"KVM list" <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM changes for 5.2 merge window
Date: Fri, 17 May 2019 10:39:56 -0700 [thread overview]
Message-ID: <CAHk-=wg1DYeY9WHP7cf-Ka-HP=6xfqrUj=FCYUCwox5vo2ANKw@mail.gmail.com> (raw)
In-Reply-To: <a8170dab-7c7d-de3d-9461-9eecb73026ff@redhat.com>
On Fri, May 17, 2019 at 4:49 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> Ouch, thanks. :/ I'll send a new pull request as soon as I finish
> testing the change you suggested.
I see that you added the trivial fix to things and re-tagged using the
same tag name. I've pulled it,
Linus
next prev parent reply other threads:[~2019-05-17 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 3:59 [GIT PULL] KVM changes for 5.2 merge window Paolo Bonzini
2019-05-17 6:22 ` Nathan Chancellor
2019-05-17 11:49 ` Paolo Bonzini
2019-05-17 17:39 ` Linus Torvalds [this message]
2019-05-17 18:35 ` pr-tracker-bot
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='CAHk-=wg1DYeY9WHP7cf-Ka-HP=6xfqrUj=FCYUCwox5vo2ANKw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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).