From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: apw@shadowen.org, "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: add filename in the summary
Date: Tue, 22 Jan 2008 14:20:48 +0100 [thread overview]
Message-ID: <4d8e3fd30801220520p14dbf5aau874d1df86415359a@mail.gmail.com> (raw)
In-Reply-To: <20080114232339.2c018647@paolo-desktop>
On Jan 14, 2008 11:23 PM, Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> Add a filename option (default to 0)
> in order to get the following summary output:
> ./scripts/checkpatch.pl --filename --file ./arch/sparc/kernel/apc.c
> ...
> ...
> ...
> ./arch/sparc/kernel/apc.c --> total: 18 errors, 3 warnings, 186 lines checked
> ---
>
> Andy,
> I wonder why checkpatch doesn't show all the command line options.
> At the moment, it only prints:
> options: -q => quiet
> --no-tree => run without a kernel tree
> --terse => one line per report
> --emacs => emacs compile window format
> --file => check a source file
> --strict => enable more subjective tests
> --root => path to the kernel tree root
>
> but I see a lot more options:
> q|quiet
> tree
> signoff
> patch
> test-type
> emacs
> terse
> file
> subjective
> strict
> root=s
> summary
> mailback
>
[patch snipped]
Hi Andy,
do you plan to document all the command line options that checkpatch
is currently accepting?
Thanks.
Ciao,
--
Paolo
http://paolo.ciarrocchi.googlepages.com/
next prev parent reply other threads:[~2008-01-22 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 22:23 Paolo Ciarrocchi
2008-01-15 18:30 ` Cyrill Gorcunov
2008-01-15 18:43 ` Paolo Ciarrocchi
2008-01-15 18:49 ` Cyrill Gorcunov
2008-01-22 13:20 ` Paolo Ciarrocchi [this message]
2008-01-28 14:38 ` Andy Whitcroft
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=4d8e3fd30801220520p14dbf5aau874d1df86415359a@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
/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®