[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1378156296.1953.117.camel@joe-AO722>
Date: Mon, 02 Sep 2013 14:11:36 -0700
From: Joe Perches <joe@...ches.com>
To: David Howells <dhowells@...hat.com>
Cc: 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>,
Wang Shilong <wangshilong1991@...il.com>
Subject: Re: [Ksummit-2013-discuss] [PATCH] checkpatch: Add comment about
updating Documentation/CodingStyle
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...
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.
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