Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1488431 > unrolled thread

[PATCH] docs: Remove space-before-label guidance from CodingStyle

Started byJonathan Corbet <corbet@lwn.net>
First post2016-09-22 00:00 +0200
Last post2016-09-22 11:30 +0200
Articles 3 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] docs: Remove space-before-label guidance from CodingStyle Jonathan Corbet <corbet@lwn.net> - 2016-09-22 00:00 +0200
    Re: [PATCH] docs: Remove space-before-label guidance from  CodingStyle Joe Perches <joe@perches.com> - 2016-09-22 00:50 +0200
    Re: [PATCH] docs: Remove space-before-label guidance from  CodingStyle Jean Delvare <jdelvare@suse.de> - 2016-09-22 11:30 +0200

#1488431 — [PATCH] docs: Remove space-before-label guidance from CodingStyle

FromJonathan Corbet <corbet@lwn.net>
Date2016-09-22 00:00 +0200
Subject[PATCH] docs: Remove space-before-label guidance from CodingStyle
Message-ID<sjXIC-5Zf-9@gated-at.bofh.it>
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>
---
 Documentation/CodingStyle | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 852253c932fe..9c61c039ccd9 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;
-- 
2.7.4

[toc] | [next] | [standalone]


#1488450 — Re: [PATCH] docs: Remove space-before-label guidance from CodingStyle

FromJoe Perches <joe@perches.com>
Date2016-09-22 00:50 +0200
SubjectRe: [PATCH] docs: Remove space-before-label guidance from CodingStyle
Message-ID<sjYuZ-6wT-3@gated-at.bofh.it>
In reply to#1488431
On Wed, 2016-09-21 at 15:54 -0600, Jonathan Corbet wrote:
> 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.

Thanks.  I believe it's better to remove this one too.

[toc] | [prev] | [next] | [standalone]


#1488684 — Re: [PATCH] docs: Remove space-before-label guidance from CodingStyle

FromJean Delvare <jdelvare@suse.de>
Date2016-09-22 11:30 +0200
SubjectRe: [PATCH] docs: Remove space-before-label guidance from CodingStyle
Message-ID<sk8ul-4tY-19@gated-at.bofh.it>
In reply to#1488431
Hi Jonathan,

On Wed, 21 Sep 2016 15:54:01 -0600, Jonathan Corbet wrote:
> 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).
> (...)
> @@ -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;

There are 2 more occurrences after this point, which you probably want
to change too.

-- 
Jean Delvare
SUSE L3 Support

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web