Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
From: Vineet Gupta
Date: Fri Jun 17 2016 - 11:36:33 EST
- Next message: Arnd Bergmann: "[PATCH] ata: fix "ering" sysfs time printing"
- Previous message: Julia Lawall: "Re: [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel"
- In reply to: Peter Zijlstra: "Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'"
- Next in thread: Ingo Molnar: "Re: 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 !
- Next message: Arnd Bergmann: "[PATCH] ata: fix "ering" sysfs time printing"
- Previous message: Julia Lawall: "Re: [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel"
- In reply to: Peter Zijlstra: "Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'"
- Next in thread: Ingo Molnar: "Re: 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 ]