From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Marcelo Tosatti <mtosatti@redhat.com>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: powerpc: allmod config build failure
Date: Tue, 05 Jan 2010 15:10:20 +0200 [thread overview]
Message-ID: <4B433A3C.3010206@redhat.com> (raw)
In-Reply-To: <04B8CF10-6D9F-477F-8500-043EA0DEBD78@suse.de>
On 01/05/2010 03:03 PM, Alexander Graf wrote:
> On 05.01.2010, at 04:32, Stephen Rothwell wrote:
>
>
>> Hi all,
>>
>> The powerpc allmodconfig build of Linus' tree has been failing like this
>> since Dec 13 (and linux-next since Nov 7):
>>
>> arch/powerpc/kvm/built-in.o:(.toc1+0x18): undefined reference to `kvm_debugfs_dir'
>>
>> $ grep KVM .config
>> CONFIG_KVM=y
>> CONFIG_KVM_BOOK3S_64_HANDLER=y
>> CONFIG_KVM_BOOK3S_64=m
>> CONFIG_KVM_EXIT_TIMING=y
>>
>> I assume that this failure was introduced by commit
>> c4f9c779f1019c7d5c61961a7c0aaaf1420d8f90 ("Include Book3s_64 target in
>> buildsystem").
>>
> Yes, and the fix is in Avi's tree already (1231730604360801d4e648c37c4b98f30850e001).
> I'm not sure how the syncing of those two happens - let's ask him.
>
Marcelo and myself collect such patches in a branch (kvm.git
kvm-updates/2.6.33) and push them to Linus. This week it's Marcelo's turn.
When sending a patch that fixes upstream (or -stable) breakage, please
not it explicitly, and we'll queue it when applying.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-05 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 3:32 powerpc: allmod config build failure Stephen Rothwell
2010-01-05 13:03 ` Alexander Graf
2010-01-05 13:10 ` Avi Kivity [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=4B433A3C.3010206@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=hollisb@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mtosatti@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.