linux-kernel - Re: checkpatch induced patches...

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 11 Feb 2015 21:36:15 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	devel@...verdev.osuosl.org, gmate.amit@...il.com,
	gregkh@...uxfoundation.org, Bas Peters <baspeters93@...il.com>,
	linux-kernel@...r.kernel.org,
	Pushpendra Singh <pushpendra.singh@...rtplayin.com>,
	manuel.schoelling@....de,
	Sudip Mukherjee <sudipm.mukherjee@...il.com>
Subject: Re: checkpatch induced patches...

On Wed, Feb 11, 2015 at 10:00:29AM -0800, Joe Perches wrote:
> I'm half tempted to submit some patch like this to
> make it difficult to use checkpatch on files outside
> of drivers/staging.
> 
> o Only allow checkpatch to be used with the -f/--file
>   option for drivers/staging/
> o Add an undocumented --force command line option

Sure.  We could try that.  I once sent a patch to make -f generate a
warning about not wasting people's time, but this is also ok.

> o Make --strict the default for drivers/staging

Ack.

regards,
dan carpenter

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