Subject: [PATCH v6 01/19] clocksource: orion: Use atomic access for shared registers

From: [email-masked] (Ezequiel Garcia)
Date: Wed, 19 Feb 2014 12:01:48 -0300

On Tue, Feb 11, 2014 at 06:47:30AM -0300, Ezequiel Garcia wrote:
> On Tue, Feb 11, 2014 at 10:11:35AM +0100, Daniel Lezcano wrote:
> > On 02/11/2014 09:30 AM, Ezequiel Garcia wrote:
> > > On Tue, Feb 11, 2014 at 01:06:43AM +0100, Daniel Lezcano wrote:
> > >> On 02/06/2014 06:20 PM, Ezequiel Garcia wrote:
> > >>> Replace the driver-specific thread-safe shared register API
> > >>> by the recently introduced atomic_io_clear_set().
> > >>>
> > >>> Cc: Daniel Lezcano <[email-masked]>
> > >>> Tested-by: Sebastian Hesselbarth <[email-masked]>
> > >>> Tested-by: Willy Tarreau <[email-masked]>
> > >>> Acked-by: Jason Cooper <[email-masked]>
> > >>> Signed-off-by: Ezequiel Garcia <[email-masked]>
> > >>
> > >> The patch looks good for me.
> > >>
> > >> Acked-by: Daniel Lezcano <[email-masked]>
> > >>
> > >
> > > Daniel,
> > >
> > > Jason acked this patch for you to take it. Or do you prefer that we
> > > merge it with the rest of the watchdog series?
> > 
> > I can pick it, but doesn't the watchdog series depend on it ?
> > 
> 
> Nope. It's indepedent of it.

Daniel,

Ping? This patch is independent of the watchdog series, and there won't
be any conflicts with it, so I think it's safe for you to take it.

-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com