[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9F6FE96B71CF29479FF1CDC8046E150339A388@039-SN1MPN1-002.039d.mgd.msft.net>
Date: Thu, 5 Jul 2012 14:20:18 +0000
From: Yoder Stuart-B08248 <B08248@...escale.com>
To: Alexander Graf <agraf@...e.de>,
Stephen Rothwell <sfr@...b.auug.org.au>
CC: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
ppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: RE: linux-next: build failure after merge of the kvm-ppc tree
> -----Original Message-----
> From: Alexander Graf [mailto:agraf@...e.de]
> Sent: Thursday, July 05, 2012 1:03 AM
> To: Stephen Rothwell
> Cc: linux-next@...r.kernel.org; linux-kernel@...r.kernel.org; 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists