[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120531125012.GA3741@zhy>
Date: Thu, 31 May 2012 20:50:12 +0800
From: Yong Zhang <yong.zhang0@...il.com>
To: Will Deacon <will.deacon@....com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rt-users@...r.kernel.org" <linux-rt-users@...r.kernel.org>,
Russell King <rmk+kernel@....linux.org.uk>,
Nicolas Pitre <nico@...aro.org>,
Catalin Marinas <Catalin.Marinas@....com>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH] ARM: cmpxchg: define __HAVE_ARCH_CMPXCHG for armv6
and later
On Thu, May 31, 2012 at 02:24:50AM +0100, Will Deacon wrote:
> Hello,
>
> On Wed, May 30, 2012 at 08:51:26AM +0100, Yong Zhang wrote:
> > diff --git a/arch/arm/include/asm/cmpxchg.h b/arch/arm/include/asm/cmpxchg.h
> > index 7eb18c1..a91b44e 100644
> > --- a/arch/arm/include/asm/cmpxchg.h
> > +++ b/arch/arm/include/asm/cmpxchg.h
> > @@ -127,6 +127,8 @@ static inline unsigned long __xchg(unsigned long x, volatile void *ptr, int size
> >
> > #else /* min ARCH >= ARMv6 */
> >
> > +#define __HAVE_ARCH_CMPXCHG 1
> > +
> > extern void __bad_cmpxchg(volatile void *ptr, int size);
>
> As long as this only requires 4-byte cmpxchg support then I think this is
> fine. It looks like that's currently the case, so:
Yes and thanks for review.
Yong
>
> Acked-by: Will Deacon <will.deacon@....com>
>
> Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists