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: <20150211224300.GD5155@mwanda>
Date:	Thu, 12 Feb 2015 01:43:00 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Pavel Machek <pavel@....cz>,
	Richard Weinberger <richard.weinberger@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	gmate.amit@...il.com, Greg KH <gregkh@...uxfoundation.org>,
	Bas Peters <baspeters93@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Pushpendra Singh <pushpendra.singh@...rtplayin.com>,
	manuel.schoelling@....de,
	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	Kalle Valo <kvalo@....qualcomm.com>
Subject: Re: checkpatch induced patches...

On Wed, Feb 11, 2015 at 12:43:03PM -0800, Joe Perches wrote:
> Maybe some help/warning text like:
> 
>   --force                    Without --force, checkpatch will not scan files
>                              using -f or --file outside of drivers/staging/...
>                              Do not use this option merely to create potential
>                              patches that are uncompiled or untested.

Everyone compiles their patches hopefully?  The problem is with patches
that aren't really a cleanup but are just done to make checkpatch happy.

I guess documenting --force is better than not documenting.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ