The patch titled
CodingStyle: start flamewar about use of braces
has been removed from the -mm tree. Its filename was
codingstyle-start-flamewar-about-use-of-braces.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: CodingStyle: start flamewar about use of braces
From: Oliver Neukum <[EMAIL PROTECTED]>
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
Cc: Tilman Schmidt <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
Documentation/CodingStyle | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff -puN
Documentation/CodingStyle~codingstyle-start-flamewar-about-use-of-braces
Documentation/CodingStyle
--- a/Documentation/CodingStyle~codingstyle-start-flamewar-about-use-of-braces
+++ a/Documentation/CodingStyle
@@ -160,6 +160,21 @@ supply of new-lines on your screen is no
25-line terminal screens here), you have more empty lines to put
comments on.
+Do not unnecessarily use braces where a single statement will do.
+
+if (condition)
+ action();
+
+This does not apply if one branch of a conditional statement is a single
+statement. Use braces in both branches.
+
+if (condition) {
+ do_this();
+ do_that();
+} else {
+ otherwise();
+}
+
3.1: Spaces
Linux kernel style for use of spaces depends (mostly) on
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
