From: Peter Zijlstra <peterz@infradead.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-snps-arc@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Anton Kolesov <Anton.Kolesov@synopsys.com>
Subject: Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
Date: Wed, 22 Jun 2016 12:24:29 +0200 [thread overview]
Message-ID: <20160622102429.GC30154@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <576A62C6.5080207@synopsys.com>
On Wed, Jun 22, 2016 at 03:34:54PM +0530, Vineet Gupta wrote:
>
> Peter the fixlet below doesn't show up in linux-next yet. Could you please do that
> soon. Our internal build lords are yelling at me :-)
>
> To keep things bisectable, it would be desirable to squash this with the orig commit !
The fix seems to be in tip/locking/arch-atomic, albeit not squashed.
Ingo?
if you're going to rebase that branch, I have one more fix for
tilepro, so let me know.
> > ---
> > arch/arc/include/asm/atomic.h | 8 --------
> > 1 file changed, 8 deletions(-)
> >
> > diff --git a/arch/arc/include/asm/atomic.h b/arch/arc/include/asm/atomic.h
> > index bd9c51cb2bfd..4e3c1b6b0806 100644
> > --- a/arch/arc/include/asm/atomic.h
> > +++ b/arch/arc/include/asm/atomic.h
> > @@ -71,7 +71,6 @@ static inline int atomic_##op##_return(int i, atomic_t *v) \
> > static inline int atomic_fetch_##op(int i, atomic_t *v) \
> > { \
> > unsigned int val, orig; \
> > - SCOND_FAIL_RETRY_VAR_DEF \
> > \
> > /* \
> > * Explicit full memory barrier needed before/after as \
> > @@ -84,11 +83,8 @@ static inline int atomic_fetch_##op(int i, atomic_t *v) \
> > " " #asm_op " %[val], %[orig], %[i] \n" \
> > " scond %[val], [%[ctr]] \n" \
> > " \n" \
> > - SCOND_FAIL_RETRY_ASM \
> > - \
> > : [val] "=&r" (val), \
> > [orig] "=&r" (orig) \
> > - SCOND_FAIL_RETRY_VARS \
> > : [ctr] "r" (&v->counter), \
> > [i] "ir" (i) \
> > : "cc"); \
> > @@ -199,10 +195,6 @@ ATOMIC_OPS(andnot, &= ~, bic)
> > ATOMIC_OPS(or, |=, or)
> > ATOMIC_OPS(xor, ^=, xor)
> >
> > -#undef SCOND_FAIL_RETRY_VAR_DEF
> > -#undef SCOND_FAIL_RETRY_ASM
> > -#undef SCOND_FAIL_RETRY_VARS
> > -
> > #else /* CONFIG_ARC_PLAT_EZNPS */
> >
> > static inline int atomic_read(const atomic_t *v)
prev parent reply other threads:[~2016-06-22 10:40 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
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 [this message]
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=20160622102429.GC30154@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Anton.Kolesov@synopsys.com \
--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 \
/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