Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Vineet Gupta
Vineet.Gupta1 at synopsys.com
Fri Jun 17 08:36:11 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 Friday 17 June 2016 05:22 PM, Peter Zijlstra wrote:
> 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.
So that is only for CONFIG_ARC_PLAT_EZNPS and very liekly not needed. Although NPS
has some design constraints which Noam knows of better !
- 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