[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080222031315.GF27894@ZenIV.linux.org.uk>
Date: Fri, 22 Feb 2008 03:13:15 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Krzysztof Halasa <khc@...waw.pl>
Cc: David Newall <davidn@...idnewall.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Adrian Bunk <bunk@...nel.org>,
Roland Dreier <rdreier@...co.com>,
Glenn Streiff <gstreiff@...Effect.com>,
Faisal Latif <flatif@...Effect.com>,
linux-kernel@...r.kernel.org, general@...ts.openfabrics.org,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <greg@...ah.com>
Subject: Re: Merging of completely unreviewed drivers
On Fri, Feb 22, 2008 at 03:23:45AM +0100, Krzysztof Halasa wrote:
> Al Viro <viro@...IV.linux.org.uk> writes:
>
> > ... if your style is lousy. I agree that situation with printks is
> > not normal in that respect and I certainly have no love for the
> > checkpatch nonsense, but pressure to keep the fucking nesting depth
> > low is a Good Thing(tm).
>
> Indeed. Unfortunately it is orthogonal to the line length limit.
Not quite. Add such things as choice of sane identifiers. And sane use of
local variables, while we are at it - things like twenty lines of
foobar[(index + 1) % BLAH]->spork.vomit[12]->field_name = <expr>;
with the only difference in the field_name, except for one line where
we have a typo and see 11 instead of intended 12, are responsible for quite
a few of such overruns.
IMO the line length overruns make good warnings. Not as in "here's a cheap
way to get more changesets", but as in "that code might have other problems
nearby" kind of heuristics.
--
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