[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140508.162727.659734236303332635.davem@davemloft.net>
Date: Thu, 08 May 2014 16:27:27 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: peterz@...radead.org
Cc: geert@...ux-m68k.org, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, mingo@...nel.org, will.deacon@....com,
paulmck@...ux.vnet.ibm.com, jesper.nilsson@...s.com,
starvik@...s.com
Subject: Re: [PATCH 07/20] arch,cris: Fold atomic_ops
From: Peter Zijlstra <peterz@...radead.org>
Date: Thu, 8 May 2014 20:17:34 +0200
> On Thu, May 08, 2014 at 01:34:51PM -0400, David Miller wrote:
>> You did this for sparc too.
>
> I did indeed.
>
> And sparc32 and sparc64 compile file without these spurious hunks.
>
> I'm sure I needed that to make it compile at one point, but I suspect
> they're remnants from the smp_mb__ shuffle which needed include file
> changes.
>
> But since then I've redone those and solved the compile issues
> differently, but these hunks stuck around...
>
> I've gone over the other patches, cris and sparc appear to be the only
> ones so affected.
>
> Just to make sure; these two hunks just went into the bit-bucket:
Thanks, with those changes:
Acked-by: David S. Miller <davem@...emloft.net>
--
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