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.18 merge window
Date: Wed, 13 Jun 2018 12:09:11 +0200 [thread overview]
Message-ID: <6570c00b-bbec-82c3-16e2-1ba96d8e263b@redhat.com> (raw)
In-Reply-To: <CA+55aFwvE5G7MV7AV4naAXdbFoszc4JNKEj_QtYqpLFfa2RXtA@mail.gmail.com>
On 13/06/2018 04:18, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 7:03 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> * x86: many bugfixes, implement more Hyper-V super powers,
>
> Uhhuh, I didn't notice this initially, because my basic sanity tests
> are with everything enabled, but this breaks the build:
>
> ERROR: "ms_hyperv" [arch/x86/kvm/kvm-intel.ko] undefined!
>
> The attached patch _may_ be the right thing to do. It's not pretty.
>
> Hmm? And why was this not found before it hit my tree?
Because I should do more "make randconfig"s, probably.
Paolo
next prev parent reply other threads:[~2018-06-13 10:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:03 Paolo Bonzini
2018-06-12 18:43 ` Linus Torvalds
2018-06-13 13:41 ` Dave Martin
2018-06-13 2:18 ` Linus Torvalds
2018-06-13 2:41 ` Linus Torvalds
2018-06-13 2:50 ` Wanpeng Li
2018-06-13 3:00 ` Linus Torvalds
2018-06-13 3:26 ` Linus Torvalds
2018-06-13 3:52 ` Linus Torvalds
2018-06-13 4:48 ` Greg Kroah-Hartman
2018-06-13 4:52 ` Linus Torvalds
2018-06-13 10:03 ` Wanpeng Li
2018-06-13 4:47 ` Greg Kroah-Hartman
2018-06-13 10:09 ` Paolo Bonzini [this message]
2018-06-13 10:59 ` Vitaly Kuznetsov
2018-06-13 14:00 ` Linus Torvalds
2018-06-13 13:56 ` Linus Torvalds
2018-06-13 14:26 ` Paolo Bonzini
2018-06-13 14:29 ` 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=6570c00b-bbec-82c3-16e2-1ba96d8e263b@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®