From: Avi Kivity <avi@redhat.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
kernel-janitors@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [kvm:auto-next 24/39] (.init.rodata+0x830): undefined reference to `x86_hyper_kvm'
Date: Thu, 26 Jul 2012 17:13:45 +0300 [thread overview]
Message-ID: <50115099.1040008@redhat.com> (raw)
In-Reply-To: <20120726140312.GA21081@localhost>
On 07/26/2012 05:03 PM, Fengguang Wu wrote:
> Hi Avi,
>
> On Thu, Jul 26, 2012 at 04:58:35PM +0300, Avi Kivity wrote:
>> On 07/26/2012 04:26 PM, Fengguang Wu wrote:
>> > Hi Raghavendra,
>> >
>> > Kernel build failed on
>> >
>> > tree: git://git.kernel.org/pub/scm/virt/kvm/kvm.git auto-next
>> > head: 12938728e8145ecd49dce97c52f10b713bcdfc94
>> > commit: f2a743473194a1ad44a85f8b63aeef9d63e5bf47 [24/39] KVM: Add config to support ple or cpu relax optimzation
>> > config: x86_64-alldefconfig (attached as .config)
>> >
>> > All related error/warning messages:
>> >
>> > arch/x86/built-in.o: In function `interrupt':
>> > (.init.rodata+0x830): undefined reference to `x86_hyper_kvm'
>>
>> Fixed by d63d3e6217c4.
>
> OK, sorry for the noise! Perhaps your tree is not rebaseable? With
> that knowledge I can arrange to not report transient errors in the
> tree, and avoid sending unnecessary noises to you.
'next' is not rebased, 'auto-next' is. Please do keep testing, if we
get too much noise we'll find a way to reduce it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-26 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 13:26 [kvm:auto-next 24/39] (.init.rodata+0x830): undefined reference to `x86_hyper_kvm' Fengguang Wu
2012-07-26 13:58 ` Avi Kivity
2012-07-26 14:03 ` Fengguang Wu
2012-07-26 14:13 ` Avi Kivity [this message]
2012-07-26 14:17 ` Fengguang Wu
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=50115099.1040008@redhat.com \
--to=avi@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=raghavendra.kt@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).