[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E9E89F2.2060103@cam.ac.uk>
Date: Wed, 19 Oct 2011 09:27:30 +0100
From: Jonathan Cameron <jic23@....ac.uk>
To: David Rientjes <rientjes@...gle.com>
CC: Joe Perches <joe@...ches.com>,
Wolfram Sang <w.sang@...gutronix.de>,
Andy Whitcroft <apw@...onical.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: checkpatch WARNING: patch prefix 'b' exists, appears to be a
-p0 patch
On 10/19/11 02:27, David Rientjes wrote:
> On Tue, 18 Oct 2011, Joe Perches wrote:
>
>>>> This started happening when I run checkpatch on pretty much anything.
>>>> triggered by the b in this snipped for example
>>>> diff --git a/arch/arm/mach-pxa/stargate2.c b/arch/arm/mach-pxa/stargate2.c
>>>> index 3f8d0af..62dc2a8 100644
>>>> --- a/arch/arm/mach-pxa/stargate2.c
>>>> +++ b/arch/arm/mach-pxa/stargate2.c
>>>> @@ -54,6 +54,8 @@
>>>> #include <linux/mfd/da903x.h>
>>>> Anyone else seeing this or have a clue what the heck is going on?
>>
>> It's done this since:
>>
>> $ git log -1 1e85572697b348b1a126520349a29654f2ae6a12
>> commit 1e85572697b348b1a126520349a29654f2ae6a12
>> Author: Wolfram Sang <w.sang@...gutronix.de>
>> Date: Tue Jan 6 14:41:24 2009 -0800
>>
>> checkpatch: Add warning for p0-patches
>>
>
> Hmm, not sure how useful that is unless both prefixes ('a' and 'b') exist.
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
As you can imagine - this is rather tedious.
As a random example see the attached patch from yesterday.
Jonathan
Download attachment "[PATCHv3 6_7] input_cma3000_d0x: Unwind reverse order of init.eml" of type "message/rfc822" (3553 bytes)
Powered by blists - more mailing lists