linux-kernel - [PATCH tip/core/rcu 0/2] Code-style fixes

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-next>] [day] [month] [year] [list]

Message-ID: <20120517221217.GA12196@linux.vnet.ibm.com>
Date:	Thu, 17 May 2012 15:12:17 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...e.hu, laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
	peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
	dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
	fweisbec@...il.com, patches@...aro.org
Subject: [PATCH tip/core/rcu 0/2] Code-style fixes

Hello!

This patch series fixes some historical code-style issues in RCU:

1.	If any branch of an if-then-else uses curly brackets, then
	all branches are supposed to.
2.	One exception to the 80-column rule is strings, which are
	not supposed to be broken across lines in deference to
	people attempting to find error messages printed by the
	kernel.

							Thanx, Paul


 b/include/linux/rcupdate.h |    3 +--
 b/kernel/rcutiny_plugin.h  |    3 ++-
 b/kernel/rcutorture.c      |    3 ++-
 b/kernel/rcutree.c         |    7 ++++---
 b/kernel/rcutree_plugin.h  |   18 ++++++++++--------
 b/kernel/rcutree_trace.c   |   25 ++++++++++++-------------
 b/lib/list_debug.c         |    6 ++----
 kernel/rcutorture.c        |   33 ++++++++++++++-------------------
 8 files changed, 47 insertions(+), 51 deletions(-)

--
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/