[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1405484621.14773.22.camel@joe-AO725>
Date: Tue, 15 Jul 2014 21:23:41 -0700
From: Joe Perches <joe@...ches.com>
To: Nick Krause <xerofoify@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, josh@...htriplett.org,
robh@...nel.org, florian.vaussard@...l.ch,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Checkpatch Feature Idea: Search directory for files with errors
and warnings with -d argument
On Wed, 2014-07-16 at 00:16 -0400, Nick Krause wrote:
> On Tue, Jul 15, 2014 at 11:38 PM, Joe Perches <joe@...ches.com> wrote:
> > On Tue, 2014-07-15 at 22:50 -0400, Nick Krause wrote:
> >> I may have not found it myself but if it doesn't exist can we write a
> >> feature for checkpatch to be able to recursively
> >> search a directory structure with a -d aRrgument in order to make it
> >> easier to search larger directories for files that still
> >> need cleanup for files having kernel coding style issues.
> >linux-kernel@...r.kernel.org
> > xargs already works fine.
> >
> > git ls-files <dir>/*.[ch] | xargs ./scripts/checkpatch.pl -f
> >
> > I suggest you only use anything like this
> > on staging directories.
> >
> >
>
> Thanks Joe,
> That was what I needed to known :). I was hitting some errors in arch,
> so I will run that to see if there are any others.
> Cheers Nick
I again suggest you _ONLY_ use checkpatch on staging.
Doing checkpatch only cleanups will not make you a
better developer nor give you a good understanding
of the code operation.
--
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