> -----Original Message----- > From: Alexander Graf [mailto:agraf@xxxxxxx] > Sent: Thursday, July 05, 2012 1:03 AM > To: Stephen Rothwell > Cc: linux-next@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Yoder Stuart-B08248; ppc-dev > Subject: Re: linux-next: build failure after merge of the kvm-ppc tree > > > On 05.07.2012, at 07:49, Stephen Rothwell wrote: > > > Hi Alexander, > > > > After merging the kvm-ppc tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > arch/powerpc/kernel/exceptions-64s.S: Assembler messages: > > arch/powerpc/kernel/exceptions-64s.S:479: Error: wrong number of operands > > arch/powerpc/kernel/exceptions-64s.S:486: Error: wrong number of operands > > arch/powerpc/kernel/exceptions-64s.S:486: Error: wrong number of operands > > arch/powerpc/kernel/exceptions-64s.S:487: Error: wrong number of operands > > arch/powerpc/kernel/exceptions-64s.S:487: Error: wrong number of operands > > arch/powerpc/kernel/exceptions-64s.S:494: Error: wrong number of operands > > arch/powerpc/kernel/exceptions-64s.S:494: Error: wrong number of operands > > > > Caused by commit bc8cc4993e19 ("PPC: use CURRENT_THREAD_INFO instead of > > open coded assembly"). The fact that this patch has problems was already > > pointed out on the linuxppc-dev mailing list and it clearly hasn't been > > build tested. > > > > I have used the version of the kvm-ppc tree from next-20120703 for today. > > Ah, yes, thanks. I kept the old, broken version in my tree to make sure I have the dependencies for (and > don't forget) the (hopefully good) patches that follow on top, but was planning to replace it once we > have a new version of the CURRENT_THREAD_INFO one. > > Stuart, could you please send a new version of the CURRENT_THREAD_INFO patch? Yes, will send that shortly. Stuart -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
