Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Peter Zijlstra
peterz at infradead.org
Fri Jun 17 07:39:42 PDT 2016
- Previous message (by thread): Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
- Next message (by thread): Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Fri, Jun 17, 2016 at 07:36:56AM -0700, Guenter Roeck wrote:
> Hi Peter,
>
> I am seeing build failures in -next when trying to build arc / arcv2 targets.
>
> arch/arc/include/asm/atomic.h:74:2: error: ‘SCOND_FAIL_RETRY_VAR_DEF’ undeclared
> arch/arc/include/asm/atomic.h:87:2: error: expected ‘:’ or ‘)’ before ‘SCOND_FAIL_RETRY_ASM’
>
> Problems seem to be caused by 'locking/atomic, arch/arc: Implement
> atomic_fetch_{add,sub,and,andnot,or,xor}()'. Both SCOND_FAIL_RETRY_VAR_DEF and
> SCOND_FAIL_RETRY_ASM are undefined.
Crud, I messed up the rebase against the backoff reverts. Lemme go do
fixups.
- Previous message (by thread): Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
- Next message (by thread): Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the linux-snps-arc
mailing list