From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: KVM list <kvm@vger.kernel.org>, kvm-ppc <kvm-ppc@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: ppc build failure
Date: Thu, 01 Apr 2010 16:28:08 +0300 [thread overview]
Message-ID: <4BB49F68.9040707@redhat.com> (raw)
I get this on a 32-bit build test:
arch/powerpc/kvm/powerpc.c: In function 'kvmppc_complete_mmio_load':
arch/powerpc/kvm/powerpc.c:338: error: 'struct kvm_vcpu_arch' has no
member named 'qpr'
arch/powerpc/kvm/powerpc.c:342: error: 'struct kvm_vcpu_arch' has no
member named 'qpr'
This is on the new branch kvm-updates/2.6.35. Please fix asap, this
branch feeds linux-next.
Stephen, if you get build errors, please drop the kvm tree.
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2010-04-01 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 13:28 Avi Kivity [this message]
[not found] ` <4BB49F68.9040707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-04-01 13:33 ` ppc build failure Alexander Graf
2010-04-01 13:54 ` Avi Kivity
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=4BB49F68.9040707@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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