[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54DBDBE0.1080000@nod.at>
Date: Wed, 11 Feb 2015 23:46:56 +0100
From: Richard Weinberger <richard@....at>
To: Dan Carpenter <dan.carpenter@...cle.com>,
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...
Am 11.02.2015 um 23:43 schrieb Dan Carpenter:
> 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.
Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing. -- Dick Brandon
Thanks,
//richard
--
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