From: Joe Perches <joe@perches.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Nick Krause <xerofoify@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
josh@joshtriplett.org, robh@kernel.org, florian.vaussard@epfl.ch,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Checkpatch Feature Idea: Search directory for files with errors and warnings with -d argument
Date: Wed, 16 Jul 2014 06:08:36 -0700 [thread overview]
Message-ID: <1405516116.14773.66.camel@joe-AO725> (raw)
In-Reply-To: <20140716080553.GE1491@thunk.org>
On Wed, 2014-07-16 at 04:05 -0400, Theodore Ts'o wrote:
> On Tue, Jul 15, 2014 at 09:39:52PM -0700, Joe Perches wrote:
[]
> > Consistency is a nicety not really a need.
> >
> > Bugs need fixing. Defects need eliminating.
> > Enhancements are appreciated. Inconsistent
> > code style is a minor annoyance.
>
> Note that patches that clean up code style can in fact be actively
> harmful, because it interferes with other developers who are sending
> patches that fix real bugs and and add new features (because the
> cleanups cause patch conflicts).
[]
> Cleanups as a part of normal code development is fine.
[]
> fixing
> every single nit that checkpatch whines about in a while adds no
> value, and in fact, can add negative value.
I think the negatives are a bit overstated.
As long as style only patches are scheduled, coordinated,
and done with a much lower priority than other real work,
there is some marginal positive value in code style
consistency.
Humans more easily read code of multiple subsystems.
Defects in existing code are sometimes uncovered.
More consistent API use is encouraged.
There are real tradeoffs to be considered in developer
time vs value though.
Even whitespace changes need review and acceptance from
upstream maintainers to make sure defects and new security
issues aren't introduced.
Upstream maintainer time is not cheap and frequently the
upstream maintainer is not cheerful either.
> (Also note that there are some local coding practices where there are
> very good reasons why the checkpatch whines need to be completely
> ignored. For example, you checkpatch doesn't deal well with the file
> format used in include/tracing/events/*.h. You need to know when the
> right thing to do is to say, "Go home, checkpatch, you're drunk.")
checkpatch can be a bit of an OCD drunk. Codetenders
have the responsibility to cut it off when its spent
too long at the file bar.
Of course it's true that checkpatch needs to have its
own bugs fixed and defects eliminated too.
prev parent reply other threads:[~2014-07-16 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 2:50 Nick Krause
2014-07-16 3:38 ` Joe Perches
2014-07-16 4:16 ` Nick Krause
2014-07-16 4:23 ` Joe Perches
2014-07-16 4:28 ` Nick Krause
2014-07-16 4:39 ` Joe Perches
2014-07-16 4:59 ` Nick Krause
2014-07-17 2:53 ` Sasha Levin
2014-07-16 8:05 ` Theodore Ts'o
2014-07-16 13:08 ` Joe Perches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1405516116.14773.66.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=florian.vaussard@epfl.ch \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tytso@mit.edu \
--cc=xerofoify@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®