LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Bernd Petrovitsch <bernd@firmix.at>,
	apw@shadowen.org, linux-kernel@vger.kernel.org,
	rdunlap@xenotime.net, jschopp@austin.ibm.com
Subject: Re: [PATCH] checkpatch.pl: allow piping
Date: Fri, 11 Jan 2008 01:36:46 -0800	[thread overview]
Message-ID: <1200044206.29897.73.camel@imap.mvista.com> (raw)
In-Reply-To: <47873833.30001@gmail.com>


On Fri, 2008-01-11 at 10:34 +0100, Jiri Slaby wrote:
> On 01/11/2008 10:30 AM, Daniel Walker wrote:
> > On Fri, 2008-01-11 at 10:23 +0100, Bernd Petrovitsch wrote:
> >> On Fre, 2008-01-11 at 10:21 +0100, Jiri Slaby wrote:
> >>> git show 9914cad54c79d0b89b1f066c0894f00e1344131c
> >> | ./scripts/checkpatch.pl -
> >>
> >> JftSoC:
> >> git show 9914cad54c79d0b89b1f066c0894f00e1344131c
> >> | ./scripts/checkpatch.pl /dev/stdin
> >> (and there a a few others) should also do the trick.
> > 
> > Not a particularly attractive command line .. Might still be a good idea
> > to add this since these two forms alluded me, and are likely to allude
> > people new to unix all together (who is more likely to be using this
> > particular tool)..
> 
> 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 ..

Daniel


  reply	other threads:[~2008-01-11  9:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080111041120.085610726@mvista.com>
2008-01-11  4:11 ` Daniel Walker
2008-01-11  8:52 ` Jiri Slaby
2008-01-11  9:17   ` Daniel Walker
2008-01-11  9:21     ` Jiri Slaby
2008-01-11  9:23       ` Bernd Petrovitsch
2008-01-11  9:30         ` Daniel Walker
2008-01-11  9:34           ` Jiri Slaby
2008-01-11  9:36             ` Daniel Walker [this message]
2008-01-11  9:41               ` Jiri Slaby
2008-01-11  9:47                 ` Daniel Walker
2008-01-11 10:11                   ` Bernd Petrovitsch
2008-01-11 11:16               ` Stefan Richter
2008-01-11 11:50                 ` Jiri Slaby
2008-01-11 17:06                   ` [PATCH] checkpatch.pl: show how to read from stdin Stefan Richter
2008-01-11 17:09                     ` Daniel Walker
2008-01-11 17:29                       ` Stefan Richter
2008-01-11 17:39                         ` Daniel Walker
2008-01-14 17:17                     ` Andy Whitcroft
2008-01-14 17:35                       ` Daniel Walker
2008-01-14 19:12                         ` Andy Whitcroft
2008-01-14 19:17                           ` Daniel Walker
2008-01-14 19:31                             ` Stefan Richter
2008-01-14 19:44                               ` Jiri Slaby
2008-01-14 19:51                               ` Daniel Walker
2008-01-11 10:08           ` [PATCH] checkpatch.pl: allow piping Bernd Petrovitsch

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=1200044206.29897.73.camel@imap.mvista.com \
    --to=dwalker@mvista.com \
    --cc=apw@shadowen.org \
    --cc=bernd@firmix.at \
    --cc=jirislaby@gmail.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --subject='Re: [PATCH] checkpatch.pl: allow piping' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).