From: Joe Perches <joe@perches.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Andy Whitcroft <apw@canonical.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: scripts: checkpatch.pl & Lindent (minor complaint)
Date: Tue, 12 Nov 2013 08:30:39 -0800 [thread overview]
Message-ID: <1384273839.4771.49.camel@joe-AO722> (raw)
In-Reply-To: <1384272557.5754.30.camel@dhcp-9-2-203-236.watson.ibm.com>
On Tue, 2013-11-12 at 11:09 -0500, Mimi Zohar wrote:
> On Tue, 2013-11-12 at 07:44 -0800, Joe Perches wrote:
> > On Tue, 2013-11-12 at 09:42 -0500, Mimi Zohar wrote:
> > > scripts/Lindent and scripts/checkpatch disagree whether the fields in a
> > > statically initialized array should be blank separated.
> > >
> > > static struct ima_rule_entry default_rules[] = {
> > > {.action = DONT_MEASURE,.fsmagic = PROC_SUPER_MAGIC,.flags = IMA_FSMAGIC},
> > >
> > > Lindent adds a blank before '.fsmagic', which checkpatch then complains
> > > about (eg. commit 75834fc3).
> >
> > Perhaps I don't understand what you mean.
>
> > Lindent _doesn't_add a blank and checkpatch
> > seems to do the right thing here.
>
> Sorry, my mistake. It's the reverse. Checkpatch complains about the
> missing blank, which Lindent then removes.
My suggestion is not to use Lindent.
If you want a semi-automated source-code reformatting tool,
use scripts/checkpatch.pl --fix
next prev parent reply other threads:[~2013-11-12 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:42 Mimi Zohar
2013-11-12 15:44 ` Joe Perches
2013-11-12 16:09 ` Mimi Zohar
2013-11-12 16:30 ` Joe Perches [this message]
2013-11-12 16:51 ` Mimi Zohar
2013-11-12 16:56 ` Joe Perches
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=1384273839.4771.49.camel@joe-AO722 \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.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®