[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160617152208.GX30154@twins.programming.kicks-ass.net>
Date: Fri, 17 Jun 2016 17:22:08 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-snps-arc@...ts.infradead.org, Ingo Molnar <mingo@...nel.org>,
Will Deacon <will.deacon@....com>
Subject: Re: Build failures in -next due to 'locking/atomic, arch/arc:
Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
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.
Powered by blists - more mailing lists