From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alexander Graf <agraf@suse.de>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the kvm-ppc tree
Date: Tue, 01 May 2012 14:55:20 +1000 [thread overview]
Message-ID: <1335848120.3621.13.camel@pasglop> (raw)
In-Reply-To: <20120501135549.5c865717b33650002f083d4a@canb.auug.org.au>
On Tue, 2012-05-01 at 13:55 +1000, Stephen Rothwell wrote:
> After merging the kvm-ppc tree, today's linux-next build
> (powerpc_ppc64_defconfig) failed like this:
>
> arch/powerpc/kvm/built-in.o: In function `.kvm_spapr_tce_release':
> book3s_64_vio.c:(.text+0x374c): undefined reference to `.kvm_put_kvm'
> arch/powerpc/kvm/built-in.o: In function
> `.kvm_vm_ioctl_create_spapr_tce':
> (.text+0x3ae8): undefined reference to `.kvm_get_kvm'
>
> Presumably caused by commit 969f70395d6d ("kvm/book3s: Make kernel
> emulated H_PUT_TCE available for "PR" KVM").
>
> I have used the kvm-ppc tree from next-20120430 for today.
Hrm, I wrote that patch :-) It used to work... Alex, probably just a
missing #include no ?
Cheers,
Ben.
next prev parent reply other threads:[~2012-05-01 4:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 3:55 linux-next: build failure after merge of the kvm-ppc tree Stephen Rothwell
2012-05-01 4:55 ` Benjamin Herrenschmidt [this message]
2012-05-01 8:37 ` Alexander Graf
2012-05-02 13:16 ` Alexander Graf
2012-05-16 7:24 Stephen Rothwell
2012-05-16 9:15 ` Paul Mackerras
2012-05-16 9:19 ` Alexander Graf
2012-07-05 5:49 Stephen Rothwell
2012-07-05 6:02 ` Alexander Graf
2012-07-05 14:20 ` Yoder Stuart-B08248
2012-10-15 0:41 Stephen Rothwell
2014-08-04 10:36 Stephen Rothwell
2014-08-05 9:19 ` Paolo Bonzini
2017-04-07 6:37 Stephen Rothwell
2017-04-28 4:31 Stephen Rothwell
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=1335848120.3621.13.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).