public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: checkpatch.pl --file gives wierd warning
Date: Thu, 12 Feb 2009 13:55:37 -0800	[thread overview]
Message-ID: <20090212215537.GA19528@kroah.com> (raw)
In-Reply-To: <20090212215040.GC6698@shadowen.org>

On Thu, Feb 12, 2009 at 09:50:40PM +0000, Andy Whitcroft wrote:
> On Thu, Feb 12, 2009 at 01:05:32PM -0800, Greg KH wrote:
> > Hi Andy,
> > 
> > With Linus's tree I get the following wierd warning when using the
> > --file option on checkpatch.pl:
> > 	$ ./scripts/checkpatch.pl --file drivers/staging/phison/phison.c
> > 	WARNING: patch prefix 'drivers' exists, appears to be a -p0 patch
> > 
> > I'm guessing that this isn't intentional :)
> > 
> > Any ideas?
> 
> heh yeah, thats fixed in my tree.  I should check the last couple of
> days testing and push those.

Ok, thanks, just wanted to make sure you knew about it.

greg k-h

      reply	other threads:[~2009-02-12 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 21:05 checkpatch.pl --file gives wierd warning Greg KH
2009-02-12 21:50 ` Andy Whitcroft
2009-02-12 21:55   ` Greg KH [this message]

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=20090212215537.GA19528@kroah.com \
    --to=greg@kroah.com \
    --cc=apw@canonical.com \
    --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