[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP9B-Q=xO8Rw_wD-tER2U1g4fKfiy01eT7rMAV6V_gCCNpy09Q@mail.gmail.com>
Date: Tue, 3 Sep 2013 08:26:21 +0800
From: Shilong Wang <wangshilong1991@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: David Howells <dhowells@...hat.com>,
Josh Triplett <josh@...htriplett.org>,
Andy Whitcroft <apw@...onical.com>,
ksummit-2013-discuss@...ts.linuxfoundation.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [Ksummit-2013-discuss] [PATCH] checkpatch: Add comment about
updating Documentation/CodingStyle
2013/9/3 Joe Perches <joe@...ches.com>:
> On Mon, 2013-09-02 at 21:50 +0100, David Howells wrote:
>> Josh Triplett <josh@...htriplett.org> wrote:
>>
>> > > There are many checkpatch rules (like semicolons) that
>> > > are not in CodingStyle.
>> >
>> > It's a rule of thumb, not a mandate. In *general*, checkpatch.pl should
>> > not be enforcing style rules that aren't documented in CodingStyle.
>>
>> Except that it becomes a mandate when someone runs it automatically against
>> every one of your patches and then sends you an email for each patch it finds
>> a checkpatch niggle against...
Agree with this..
But using checkpatch.pl, i found there are *so many* patches that have
warnings or errors.
As far as i know, patches with checkpatch.pl's errors should be
avoided at least unless
there is a *bug* in checkpatch.pl!
>
> I think that any robot sending such checkpatch-only
> emails should be disabled.
>
> I know of 2 email robots.
>
> Fengguang Wu's very useful build robot
> sends out emails on build failures.
> I think that's great.
>
> Wang Shilong <wangshilong1991@...il.com>
> sent me an automated checkpatch email I
> thought was not useful.
I am sorry if i give you any trouble, i have disabled it(in fact, it
only has run for a day!)
Thanks,
wang
>
> Does anyone know of other checkpatch robots?
>
>
--
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