From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
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] Second batch of KVM changes for Linux 4.15
Date: Thu, 23 Nov 2017 17:50:53 -1000 [thread overview]
Message-ID: <CA+55aFzMz0CoACGODnZmWsKf5buLMq1s63iHKcvT1F+RUrWpZQ@mail.gmail.com> (raw)
In-Reply-To: <1511222806-11512-1-git-send-email-pbonzini@redhat.com>
On Mon, Nov 20, 2017 at 2:06 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> I am not including the host side of AMD SEV, because it wouldn't have gotten
> enough time in linux-next even with a "regular-length" merge window. It
> will be in 4.16.
So I pulled it, but then checked,
None of this was in linux-next 20171117 either,
So I unpulled it,
Linus
next prev parent reply other threads:[~2017-11-24 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 0:06 [GIT PULL] Second batch of KVM changes for Linux 4.15 Paolo Bonzini
2017-11-24 3:50 ` Linus Torvalds [this message]
2017-11-24 9:36 ` Paolo Bonzini
[not found] ` <CA+55aFwwvdL2t9POHzQp3BEzOGyNXh4KWwda1=r26QcujJ-5rQ@mail.gmail.com>
2017-11-27 10:35 ` Paolo Bonzini
2017-11-27 19:16 ` 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=CA+55aFzMz0CoACGODnZmWsKf5buLMq1s63iHKcvT1F+RUrWpZQ@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).