From: Jonathan Corbet <corbet@lwn.net>
Date: Wed, 21 Sep 2016 21:46:18 +0000 (-0600)
Subject: docs: Remove space-before-label guidance from CodingStyle
X-Git-Tag: v5.15~12645^2~4
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=79c70c304b0b443429b2a0019518532c5162817a;p=platform%2Fkernel%2Flinux-starfive.git

docs: Remove space-before-label guidance from CodingStyle

Recent discussion has made it clear that there is no community consensus on
this particular rule.  Remove it now, lest it inspire yet another set of
unwanted "cleanup" patches.

This partially reverts 865a1caa4b6b (CodingStyle: Clarify and complete
chapter 7).

Cc: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
---

diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 852253c..9c61c03 100644
--- a/Documentation/CodingStyle
+++ b/Documentation/CodingStyle
@@ -451,9 +451,6 @@ Avoid using GW-BASIC names like ``err1:`` and ``err2:``, as you would have to
 renumber them if you ever add or remove exit paths, and they make correctness
 difficult to verify anyway.
 
-It is advised to indent labels with a single space (not tab), so that
-``diff -p`` does not confuse labels with functions.
-
 The rationale for using gotos is:
 
 - unconditional statements are easier to understand and follow
@@ -481,7 +478,7 @@ The rationale for using gotos is:
 			goto out_buffer;
 		}
 		...
-	 out_free_buffer:
+	out_free_buffer:
 		kfree(buffer);
 		return result;
 	}
@@ -490,7 +487,7 @@ A common type of bug to be aware of is ``one err bugs`` which look like this:
 
 .. code-block:: c
 
-	 err:
+	err:
 		kfree(foo->bar);
 		kfree(foo);
 		return ret;