mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, Seunghun Lee <waydi1@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Improve missing blank line after declarations test
Date: Mon, 05 May 2014 15:35:43 -0700	[thread overview]
Message-ID: <1399329343.27516.2.camel@joe-AO725> (raw)
In-Reply-To: <20140505151531.af8e82be3a0c4800f0051de2@linux-foundation.org>

On Mon, 2014-05-05 at 15:15 -0700, Andrew Morton wrote:
> On Mon, 05 May 2014 13:12:16 -0700 Joe Perches <joe@perches.com> wrote:
> 
> > A couple more modifications to the declarations tests.
> > 
> > o Declarations can also be bitfields so exclude things with a colon
> > o Make sure the current and previous lines are indented the same
> >   to avoid matching some macro where a struct type is passed on
> >   the previous line like:
> > 
> > 		next = list_entry(buffer->entry.next,
> > 				  struct binder_buffer, entry);
> > 		if (buffer_start_page(next) == buffer_end_page(buffer)) 
> 
> So checkpatch-always-warn-on-missing-blank-line-after-variable-declaration-block.patch
> is stuck in -mm while I evaluate its effects.  Thus far that evaluation
> has been "super non-intrusive", because the patch doesn't actually
> do anything.
[]
> @@ -67,6 +68,7 @@ long vfs_truncate(struct path *path, lof
>  {
>  	struct inode *inode;
>  	long error;
> +	wobble();
>  
>  	inode = path->dentry->d_inode;

Patch content can be a bit odd when lines are
both added and deleted so checkpatch bleats
only when both lines are added.

+	int foo;
+	wibble();

generates a complaint.

 	int foo;
+	wibble_wobble();

does not.


  reply	other threads:[~2014-05-05 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 16:59 [PATCH] staging: android: fix missing a blank line after declarations Seunghun Lee
2014-04-29 17:32 ` Dan Carpenter
2014-05-03 23:43   ` Greg KH
2014-05-05  9:59     ` Dan Carpenter
2014-05-05 19:51       ` Joe Perches
2014-05-05 20:12         ` [PATCH] checkpatch: Improve missing blank line after declarations test Joe Perches
2014-05-05 22:15           ` Andrew Morton
2014-05-05 22:35             ` Joe Perches [this message]
2014-05-05 22:42               ` Andrew Morton

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=1399329343.27516.2.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waydi1@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®