mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: David Rientjes <rientjes@google.com>,
	Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: checkpatch WARNING: patch prefix 'b' exists, appears to be a -p0 patch
Date: Wed, 19 Oct 2011 12:04:23 +0100	[thread overview]
Message-ID: <4E9EAEB7.6080601@cam.ac.uk> (raw)
In-Reply-To: <20111019102630.GE3217@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]

On 10/19/11 11:26, Wolfram Sang wrote:
> 
>> Sorry, I missed one detail. This warning is firing on every patch including
>> any I pull off mailing lists or produce with git format-patch
> 
> So, I assume you have a directory named 'b' in the kernel-root-dir?
File, but good call.  Thanks.  All back to normal now.
I'll have to be more creative with naming my random temporary diff files ;)
(or remember to delete them afterwards).
> 
> The p1-detection is heuristic and can always be fooled, so I don't think
> extending the logic will help. If too many users think it is annoying,
> it may be better to remove it. I do think, however, that it might help
> users sending in their first patches, so I'd prefer to keep it.
> Experienced users have the option to use something like "--ignore
> PATCH_PREFIX" in their .checkpatch.conf. I vote for improving the error
> message but won't oppose a removal if that is what is wanted.

Maybe something as simple as a comment in the checkpatch source
to say that such a file / directory can cause false positives?

Thanks again

Jonathan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2011-10-19 11:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 15:03 Jonathan Cameron
2011-10-18 23:44 ` David Rientjes
2011-10-19  0:01   ` Joe Perches
2011-10-19  1:27     ` David Rientjes
2011-10-19  8:27       ` Jonathan Cameron
2011-10-19 10:26         ` Wolfram Sang
2011-10-19 11:04           ` Jonathan Cameron [this message]
2011-10-19 11:22             ` Wolfram Sang
2011-10-19 11:32               ` Jonathan Cameron
2011-10-19 16:17               ` 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=4E9EAEB7.6080601@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@google.com \
    --cc=w.sang@pengutronix.de \
    /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®