linux-kernel - Re: CodingStyle parenthesis alignment: was: Re: align to open paren

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1429147763.2850.33.camel@perches.com>
Date:	Wed, 15 Apr 2015 18:29:23 -0700
From:	Joe Perches <joe@...ches.com>
To:	"Hubbe, Allen" <Allen.Hubbe@....com>
Cc:	"apw@...onical.com" <apw@...onical.com>,
	LKML <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: CodingStyle parenthesis alignment: was: Re: align to open paren

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...



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/