[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 07 Jul 2012 10:36:49 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Grant Grundler <grundler@...omium.org>
Cc: Christian Riesch <christian.riesch@...cron.at>,
netdev@...r.kernel.org, Oliver Neukum <oneukum@...e.de>,
Eric Dumazet <edumazet@...gle.com>,
Allan Chou <allan@...x.com.tw>,
Mark Lord <kernel@...savvy.com>,
Ming Lei <tom.leiming@...il.com>,
Michael Riesch <michael@...sch.at>
Subject: Re: [PATCH 1/4] asix: Fix checkpatch warnings
On Fri, 2012-07-06 at 14:43 -0700, Grant Grundler wrote:
> Christian is clearly running checkpatch.pl as suggested in
> Documentation/SubmittingPatches. He missed the part about "You should
> be able to justify all violations that remain in your patch." and/or
> didn't know about "fixing existing code is a waste of time".
>
> Given the extent of the changes Christian is making (factoring out
> asix common code from model specific code), it's helpful to have clean
> checkpatch runs. I don't believe it's a waste of time to apply this
> patch. Is it conflicting with any other code changes that are in
> flight now?
It was a waste of time for me, at least (Since I was CCed for the
patch), and just sent my personal opinion on checkpatch generated
patches.
Splitting a perfectly good line :
netdev_err(dev->net, "Error reading PHYID register: %02x\n", ret);
into
netdev_err(dev->net, "Error reading PHYID register: %02x\n",
ret);
is a clear sign of how stupid checkpatch is.
And fact we can spend time on discussions about checkpatch is
astonishing.
Automatic tools should be smart and ease people tasks, not
slowing them.
Note that Christian patch serie in itself is good, I don't want to block
it at all.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists