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.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
On 05.07.2012, at 07:49, Stephen Rothwell wrote:
Hi Alexander,
=20
After merging the kvm-ppc tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
=20
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
=20
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.
=20
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?
Alex
-----Original Message-----
From: Alexander Graf [mailto:agraf@suse.de]
Sent: Thursday, July 05, 2012 1:03 AM
To: Stephen Rothwell
Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Yoder Stuar=
t-B08248; ppc-dev
Subject: Re: linux-next: build failure after merge of the kvm-ppc tree
=20
=20
On 05.07.2012, at 07:49, Stephen Rothwell wrote:
=20
quoted
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 operan=
ds
quoted
arch/powerpc/kernel/exceptions-64s.S:486: Error: wrong number of operan=
ds
quoted
arch/powerpc/kernel/exceptions-64s.S:486: Error: wrong number of operan=
ds
quoted
arch/powerpc/kernel/exceptions-64s.S:487: Error: wrong number of operan=
ds
quoted
arch/powerpc/kernel/exceptions-64s.S:487: Error: wrong number of operan=
ds
quoted
arch/powerpc/kernel/exceptions-64s.S:494: Error: wrong number of operan=
ds
quoted
arch/powerpc/kernel/exceptions-64s.S:494: Error: wrong number of operan=
ds
quoted
Caused by commit bc8cc4993e19 ("PPC: use CURRENT_THREAD_INFO instead of
open coded assembly"). The fact that this patch has problems was alrea=
dy
quoted
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 toda=
y.
=20
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 pl=
anning to replace it once we
have a new version of the CURRENT_THREAD_INFO one.
=20
Stuart, could you please send a new version of the CURRENT_THREAD_INFO pa=
tch?
Yes, will send that shortly.
Stuart