All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jean Delvare <jdelvare@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Wolfram Sang <wsa@the-dreams.de>, Tim Waugh <tim@cyberelk.net>,
	Willy Tarreau <willy@meta-x.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	devel@driverdev.osuosl.org
Subject: [RFC PATCH] checkpatch: check for 2 or more spaces around assignment of a declaration
Date: Wed, 20 May 2015 18:02:06 -0700	[thread overview]
Message-ID: <1432170126.20840.22.camel@perches.com> (raw)
In-Reply-To: <20150520195918.1c150979@endymion.delvare>

On Wed, 2015-05-20 at 19:59 +0200, Jean Delvare wrote:
> On Wed, 20 May 2015 22:44:52 +0530, Sudip Mukherjee wrote:
> > On Wed, May 20, 2015 at 05:49:07PM +0200, Wolfram Sang wrote:
> > > On Wed, May 20, 2015 at 08:57:00PM +0530, Sudip Mukherjee wrote:
> > > >  static struct parport_driver i2c_parport_driver = {
> > > > -	.name	= "i2c-parport",
> > > > -	.attach	= i2c_parport_attach,
> > > > -	.detach	= i2c_parport_detach,
> > > > +	.name		= "i2c-parport",
> > > > +	.match_port	= i2c_parport_attach,
> > > > +	.detach		= i2c_parport_detach,
> > > > +	.devmodel	= true,
> > > 
> > > Minor nit: I prefer to not use tabs but a single space after the struct
> > > member names. Less hazzle in the future and still readable IMO.
> >
> > It was having space originally. I changed that into tab as it was
> > looking good with them as aligned.
> 
> As the driver maintainer, I am fine with both unaligned or tab-aligned.
> Space-aligned as I did originally was not a good idea, I admit.

Perhaps space aligned declarations should have some
checkpatch --strict warning for 2 or more spaces
around any assignment of the declaration.

	int a   = 1;		// 2+ spaces before =
	int b	=  2;		// 2+ spaces after =
	int c	=	3;	// uses tabs around =, no warning
	int d		= 4;	// uses 2 tabs before =, no warning
	
Something like:
---
 scripts/checkpatch.pl | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 89b1df4..8f9d26f 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3902,6 +3902,13 @@ sub process {
 			    "multiple assignments should be avoided\n" . $herecurr);
 		}
 
+# check for space aligned declarations
+		if ($line =~ /^.\s*(?:$Declare|$DeclareMisordered)\s*$Ident {2,}=\s*(?:$Lval|$Constant|$String)/ ||
+		    $line =~ /^.\s*(?:$Declare|$DeclareMisordered)\s*$Ident\s*= {2,}(?:$Lval|$Constant|$String)/) {
+			CHK("SPACING",
+			    "Avoid multiple space assigments - prefer a single space or tabs\n" . $herecurr);
+		}
+
 ## # check for multiple declarations, allowing for a function declaration
 ## # continuation.
 ## 		if ($line =~ /^.\s*$Type\s+$Ident(?:\s*=[^,{]*)?\s*,\s*$Ident.*/ &&

  reply	other threads:[~2015-05-21  1:02 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 15:26 [PATCH 0/6] use devicemodel with parport Sudip Mukherjee
2015-05-20 15:26 ` Sudip Mukherjee
2015-05-20 15:26 ` [PATCH 1/6] parport: add device-model to parport subsystem Sudip Mukherjee
2015-05-20 15:26   ` Sudip Mukherjee
2015-05-20 15:26 ` [PATCH 2/6] staging: panel: use new parport device model Sudip Mukherjee
2015-05-20 15:26 ` [PATCH 3/6] i2c-parport: define ports to connect Sudip Mukherjee
2015-05-20 15:26   ` Sudip Mukherjee
2015-05-20 15:46   ` Wolfram Sang
2015-05-20 15:46     ` Wolfram Sang
2015-05-20 15:27 ` [PATCH 4/6] i2c-parport: use new parport device model Sudip Mukherjee
2015-05-20 15:49   ` Wolfram Sang
2015-05-20 17:14     ` Sudip Mukherjee
2015-05-20 17:14       ` Sudip Mukherjee
2015-05-20 17:35       ` Wolfram Sang
2015-05-20 17:35         ` Wolfram Sang
2015-05-20 17:59       ` Jean Delvare
2015-05-20 17:59         ` Jean Delvare
2015-05-21  1:02         ` Joe Perches [this message]
2015-05-21  5:48           ` [RFC PATCH] checkpatch: check for 2 or more spaces around assignment of a declaration Willy Tarreau
2015-05-21  5:48             ` Willy Tarreau
2015-05-21  6:16   ` [PATCH v2 4/6] i2c-parport: use new parport device model Sudip Mukherjee
2015-05-21  6:16     ` Sudip Mukherjee
2015-05-20 15:27 ` [PATCH 5/6] paride: " Sudip Mukherjee
2015-05-20 15:27   ` Sudip Mukherjee
2015-05-20 15:27 ` [PATCH 6/6] MAINTAINERS: maintain parport Sudip Mukherjee
2015-05-20 15:46   ` Richard Weinberger
2015-05-20 15:46     ` Richard Weinberger
2015-05-20 16:28     ` Joe Perches
2015-05-20 16:28       ` Joe Perches
2015-05-20 17:31       ` Sudip Mukherjee
2015-05-20 17:31         ` Sudip Mukherjee
2015-05-20 16:33     ` One Thousand Gnomes
2015-05-20 16:33       ` One Thousand Gnomes
2015-05-20 20:36       ` Richard Weinberger
     [not found]         ` <555CF034.5090704-/L3Ra7n9ekc@public.gmane.org>
2015-05-21  5:59           ` Sudip Mukherjee
2015-05-21  5:59             ` Sudip Mukherjee
2015-05-21  5:51     ` Willy Tarreau
2015-05-21  5:51       ` Willy Tarreau
2015-05-21  6:09       ` Greg Kroah-Hartman
2015-05-21  6:09         ` Greg Kroah-Hartman
2015-05-31 22:05 ` [PATCH 0/6] use devicemodel with parport Greg Kroah-Hartman
2015-05-31 22:05   ` Greg Kroah-Hartman
     [not found]   ` <20150531220530.GF13872-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-06-01  5:46     ` Sudip Mukherjee
2015-06-01  5:46       ` Sudip Mukherjee
2015-06-01  6:18       ` Greg Kroah-Hartman
2015-06-01  6:18         ` Greg Kroah-Hartman
     [not found]         ` <20150601061811.GA5103-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-06-01  8:34           ` Sudip Mukherjee
2015-06-01  8:34             ` Sudip Mukherjee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1432170126.20840.22.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tim@cyberelk.net \
    --cc=willy@meta-x.org \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.