[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvzY=uZcoa1rCJSqokLfDgXtZ=-sD6mc638Qxh-HDwYwXw@mail.gmail.com>
Date: Wed, 11 Feb 2015 21:02:31 +0100
From: Richard Weinberger <richard.weinberger@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Joe Perches <joe@...ches.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>
Subject: Re: checkpatch induced patches...
On Wed, Feb 11, 2015 at 7:36 PM, Dan Carpenter <dan.carpenter@...cle.com> wrote:
> 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.
FYI: We had already a heated debate on that topic.
https://lkml.org/lkml/2014/7/17/415
--
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