Re: checkpatch induced patches...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2015-02-11 at 21:02 +0100, Richard Weinberger wrote:
> On Wed, Feb 11, 2015 at 7:36 PM, Dan Carpenter <dan.carpenter@xxxxxxxxxx> 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

Yeah, I remember.

It's always a pleasure to chat with Borislav.

This is basically a patch that implements my suggestion
in that thread.

https://lkml.org/lkml/2014/7/17/427

I wonder if the undocumented --force option is acceptable
to Pavel and Kalle.

_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel




[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux