From: Peter Zijlstra <peterz@infradead.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-snps-arc@lists.infradead.org,
Ingo Molnar <mingo@kernel.org>, Will Deacon <will.deacon@arm.com>
Subject: Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Date: Fri, 17 Jun 2016 17:22:08 +0200 [thread overview]
Message-ID: <20160617152208.GX30154@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <576410AB.6050204@synopsys.com>
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.
next prev parent reply other threads:[~2016-06-17 15:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:36 Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Guenter Roeck
2016-06-17 14:39 ` Peter Zijlstra
2016-06-17 14:41 ` Peter Zijlstra
2016-06-17 14:52 ` Guenter Roeck
2016-06-17 15:00 ` Vineet Gupta
2016-06-17 15:22 ` Peter Zijlstra [this message]
2016-06-17 15:36 ` Vineet Gupta
2016-06-17 16:04 ` Ingo Molnar
2016-06-17 16:13 ` Peter Zijlstra
2016-06-17 20:22 ` Vineet Gupta
2016-06-17 21:27 ` Guenter Roeck
2016-06-18 7:05 ` Peter Zijlstra
2016-06-18 10:17 ` cross compilers [was build failure of sorts] Peter Zijlstra
2016-06-21 5:29 ` Vineet Gupta
2016-06-21 7:43 ` Peter Zijlstra
2016-06-21 9:28 ` Vineet Gupta
2016-06-21 9:45 ` Peter Zijlstra
2016-06-21 9:59 ` Vineet Gupta
2016-06-21 10:04 ` Peter Zijlstra
2016-06-22 10:04 ` Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()' Vineet Gupta
2016-06-22 10:24 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160617152208.GX30154@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=mingo@kernel.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox