From: Joe Perches <joe@perches.com>
To: "Hubbe, Allen" <Allen.Hubbe@emc.com>
Cc: "apw@canonical.com" <apw@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: CodingStyle parenthesis alignment: was: Re: align to open paren
Date: Wed, 15 Apr 2015 18:29:23 -0700 [thread overview]
Message-ID: <1429147763.2850.33.camel@perches.com> (raw)
In-Reply-To: <40F65EF2B5E2254199711F58E3ACB84D781CD94F@MX104CL02.corp.emc.com>
On Wed, 2015-04-15 at 21:54 +0000, Hubbe, Allen wrote:
> I ran with the --fix option, and it changed every rejected indent to
> match the column of the open paren. That's probably what you want,
> since it's the most consistent with the previous behavior. The
> difference is that it does not fix lines that are no longer rejected,
> like if they are indented by two per paren. The test file and output
> are attached.
There might be some utility adding a --style=<foo>
switch so checkpatch can appropriately warn on
K&R vs linux vs bsd vs gnu vs otb, etc...
prev parent reply other threads:[~2015-04-16 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40F65EF2B5E2254199711F58E3ACB84D781CD892@MX104CL02.corp.emc.com>
2015-04-15 21:06 ` CodingStyle parenthesis alignment: was: Re: align to open paren Joe Perches
2015-04-15 21:54 ` Hubbe, Allen
2015-04-16 1:29 ` Joe Perches [this message]
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=1429147763.2850.33.camel@perches.com \
--to=joe@perches.com \
--cc=Allen.Hubbe@emc.com \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).