linux-kernel - Re: [RFC PATCH v2 1/1] rename {before/after}_atomic_{inc/dec} to {before/after}

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 May 2014 08:43:02 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Pranith Kumar <bobby.prani@...il.com>
Cc:	paulmck@...ux.vnet.ibm.com, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2 1/1] rename {before/after}_atomic_{inc/dec} to
 {before/after}_atomic

On Thu, May 29, 2014 at 12:28:10AM -0400, Pranith Kumar wrote:
>  There is no reason to have separete barriers for atomic_inc and atomic_dec. 
>  All the architectures use the same barriers for both.
> 
>  We can simplify it and just have {before/after}_atomic after renaming.
> 
>  I used coccinelle script to do the renames in the C files and did the rename by hand in the headers.
> 
> v2: 
> * remove duplicate macros in missed files
> * correct indentation
> 
> Signed-off-by: Pranith Kumar <bobby.prani@...il.com>

See http://marc.info/?l=linux-kernel&m=139782635207358 and the 20 or so
patches afterwards.

This has already been done. See a -next tree or so near you.
--
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/