Re: [kvm:auto-next 24/39] (.init.rodata+0x830): undefined reference to `x86_hyper_kvm'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 26, 2012 at 05:13:45PM +0300, Avi Kivity wrote:
> 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.

Got it! I actually do per-branch control policies :-) I've set it up
to report every build error in kvm/auto-next and to only report errors
that still remain at kvm/next/HEAD.

Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux