From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>, torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, rkrcmar@redhat.com,
kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Dan Williams <dan.j.williams@intel.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Paul Mackerras <paulus@ozlabs.org>
Subject: Re: [GIT PULL] KVM changes for 4.8 merge window
Date: Wed, 3 Aug 2016 13:00:18 +0200 [thread overview]
Message-ID: <c2b73599-0832-a0af-2ca5-b4c816ec6766@redhat.com> (raw)
In-Reply-To: <87d1lql58t.fsf@concordia.ellerman.id.au>
On 03/08/2016 08:46, Michael Ellerman wrote:
>> Considering the h in "hmi" is for hypervisor,
>
> Well hypervisor != KVM.
>
> Though in this case hmi.c was pretty safe because it was new code. But
> if I'd received a powerpc patch to hmi.c I wouldn't have thought to
> check if it conflicted with the KVM tree.
This, together with the fact that hmi.c does nothing if KVM is
inactive, suggests to me that hmi.c should be in arch/powerpc/kvm.
I'll send a patch soo; I don't care who merges it, but a topic
branch would be appropriate. ;)
Paolo
prev parent reply other threads:[~2016-08-03 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:37 Paolo Bonzini
2016-08-02 18:02 ` Christian Borntraeger
2016-08-02 18:42 ` Linus Torvalds
2016-08-02 20:17 ` Linus Torvalds
2016-08-02 20:49 ` Christian Borntraeger
2016-08-02 21:36 ` Martin Schwidefsky
2016-08-02 21:46 ` Linus Torvalds
2016-08-02 18:55 ` Paolo Bonzini
2016-08-03 3:21 ` Michael Ellerman
2016-08-03 6:26 ` Paolo Bonzini
2016-08-03 6:46 ` Michael Ellerman
2016-08-03 11:00 ` Paolo Bonzini [this message]
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=c2b73599-0832-a0af-2ca5-b4c816ec6766@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.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®