From: Alexander Graf <agraf@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: Linuxppc-dev@ozlabs.org, subrata@linux.vnet.ibm.com,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Make long relocations be ulong
Date: Mon, 19 Jul 2010 17:33:59 +0200 [thread overview]
Message-ID: <4C447067.2030205@suse.de> (raw)
In-Reply-To: <4C446FA0.8050403@redhat.com>
Avi Kivity wrote:
> On 07/19/2010 05:54 PM, Alexander Graf wrote:
>> I'm not sure which tree this should go through. Avi and Ben, please
>> coordinate this.
>> ---
>> arch/powerpc/include/asm/kvm_book3s.h | 4 ++--
>> arch/powerpc/kvm/book3s_rmhandlers.S | 4 ++--
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
>>
>
> The diffstat suggests kvm.git.
>
> Is this broken in Linus' tree, or just kvm.git?
I got the bug report through linuxppc-dev, so I assume it's broken in
Linus' tree. In fact, that code has been around for a while already, so
it should even be in 2.6.24.
Alex
prev parent reply other threads:[~2010-07-19 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 14:54 [PATCH] KVM: PPC: Make long relocations be ulong Alexander Graf
2010-07-19 15:30 ` Avi Kivity
2010-07-19 15:33 ` Alexander Graf [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=4C447067.2030205@suse.de \
--to=agraf@suse.de \
--cc=Linuxppc-dev@ozlabs.org \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=subrata@linux.vnet.ibm.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).