[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <485681BA.4060808@s5r6.in-berlin.de>
Date: Mon, 16 Jun 2008 17:07:38 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Németh Márton <nm127@...email.hu>
CC: David Newall <davidn@...idnewall.com>,
Jeff Garzik <jgarzik@...ox.com>, netdev@...r.kernel.org,
Trivial Patch Monkey <trivial@...nel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] 8139too: clean up spaces and TABs
Németh Márton wrote:
> I have chosen the checkpatch.pl's output to compare the
> whether the old and the new code are better or not. Maybe that was a mistake.
Well, running checkpatch on source files (rather than patches) and
fixing the files up according to checkpatch's output and own good
judgement has two uses:
- bring new unmerged code into shape before submission,
- bring older mainline code into the canonical form as a basis
for further work. You certainly saw how lots and lots of such
checkpatch-assisted cleanups went into arch/x86. That's because
they were found useful for the work on unifying the two x86
architecture subtrees.
So, a coding style rework has its use even on legacy code if people have
plans with the code. But keep in mind that (a) the whitespace rules
aren't hard and universally agreed upon rules, (b) coding style has a
number of other aspects of arguably greater importance than whitespace
style, like proper modularization, good choices of names, use of common
idioms and APIs instead of own inventions, and so on.
--
Stefan Richter
-=====-==--- -==- =----
http://arcgraph.de/sr/
--
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