From: Joe Perches <joe@perches.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
josh@joshtriplett.org, robh@kernel.org, florian.vaussard@epfl.ch,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Checkpatch Feature Idea: Search directory for files with errors and warnings with -d argument
Date: Tue, 15 Jul 2014 21:23:41 -0700 [thread overview]
Message-ID: <1405484621.14773.22.camel@joe-AO725> (raw)
In-Reply-To: <CAPDOMVhSosu-WZkBo+mKs3mJ+2+W-rBq0LFUnU_Lnzn=jR7=wg@mail.gmail.com>
On Wed, 2014-07-16 at 00:16 -0400, Nick Krause wrote:
> On Tue, Jul 15, 2014 at 11:38 PM, Joe Perches <joe@perches.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@vger.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.
next prev parent reply other threads:[~2014-07-16 4:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 2:50 Nick Krause
2014-07-16 3:38 ` Joe Perches
2014-07-16 4:16 ` Nick Krause
2014-07-16 4:23 ` Joe Perches [this message]
2014-07-16 4:28 ` Nick Krause
2014-07-16 4:39 ` Joe Perches
2014-07-16 4:59 ` Nick Krause
2014-07-17 2:53 ` Sasha Levin
2014-07-16 8:05 ` Theodore Ts'o
2014-07-16 13:08 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1405484621.14773.22.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=florian.vaussard@epfl.ch \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xerofoify@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®