[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4787502B.2020606@s5r6.in-berlin.de>
Date: Fri, 11 Jan 2008 12:16:59 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Daniel Walker <dwalker@...sta.com>
CC: Jiri Slaby <jirislaby@...il.com>,
Bernd Petrovitsch <bernd@...mix.at>, apw@...dowen.org,
linux-kernel@...r.kernel.org, rdunlap@...otime.net,
jschopp@...tin.ibm.com
Subject: Re: [PATCH] checkpatch.pl: allow piping
Daniel Walker wrote:
> On Fri, 2008-01-11 at 10:34 +0100, Jiri Slaby wrote:
>> >> On Fre, 2008-01-11 at 10:21 +0100, Jiri Slaby wrote:
>> >>> git show 9914cad54c79d0b89b1f066c0894f00e1344131c
>> >> | ./scripts/checkpatch.pl -
>> If somebody is hacking kernel, I think he should know the - trick used in many
>> programs, but do not consider this as a nack.
>
> I'm hacking the kernel, and I didn't know the - trick .. So you have
> your testing case all in one with the patch submitter ..
How about
if ($#ARGV < 0) {
print "usage: $P [options] patchfile\n";
print "version: $V\n";
print "options: -q => quiet\n";
print " --no-tree => run without a kernel tree\n";
print " --terse => one line per report\n";
print " --emacs => emacs compile window format\n";
print " --file => check a source file\n";
print " --strict => enable more subjective tests\n";
print " --root => path to the kernel tree root\n";
+ print "When patchfile is -, read standard input.\n";
exit(1);
}
--
Stefan Richter
-=====-==--- ---= -=-==
http://arcgraph.de/sr/
--
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