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 08:22:08 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 ]
Question; why does atomic_read() have a full memory clobber on arc?
Will thinks its because you don't use a memory constraint for *v.
- 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