linux-kernel - Re: checkpatch: kill the bogus camelcase check

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1365604558.27174.36.camel@joe-AO722>
Date:	Wed, 10 Apr 2013 07:35:58 -0700
From:	Joe Perches <joe@...ches.com>
To:	Andy Whitcroft <apw@...onical.com>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: checkpatch: kill the bogus camelcase check

On Wed, 2013-04-10 at 14:26 +0100, Andy Whitcroft wrote:
> On Tue, Apr 09, 2013 at 02:50:54PM -0700, James Bottomley wrote:
> > It's making checkpatch unusable on most drivers because it's spewing
> > tons of bogus warnings.  The problem is the assumption that studly caps
> > is always wrong: it isn't if the variables are named after the various
> > conventions in the hardware programming guides (which are usually
> > written by Microsoft people).
> > 
> > In order to encourage people to use checkpatch, it has to be *useful* it
> > can't stray too far into dogmatic things like this that are essentially
> > unfixable by most people who submit patches.
> > 
> > Signed-off-by: James Bottomley <JBottomley@...allels.com>
> 
> Joe, perhaps this could become a strict check?

or maybe exclude drivers/scsi and include/scsi/

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