[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1609221702050.2981@hadrien>
Date: Thu, 22 Sep 2016 17:05:37 +0200 (CEST)
From: Julia Lawall <julia.lawall@...6.fr>
To: Jean Delvare <jdelvare@...e.de>
cc: Al Viro <viro@...IV.linux.org.uk>, Joe Perches <joe@...ches.com>,
Julia Lawall <julia.lawall@...6.fr>,
Ilya Dryomov <idryomov@...il.com>,
Andy Whitcroft <apw@...onical.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>,
Ceph Development <ceph-devel@...r.kernel.org>,
Alex Elder <elder@...nel.org>, Sage Weil <sage@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
linux-doc@...r.kernel.org
Subject: Re: "CodingStyle: Clarify and complete chapter 7" in docs-next
> > The main intent of checkpatch these days appears to be providing an easy
> > way of thoughtless inflation of commit counts, everything else be damned.
> > Make-work, in other words.
>
> Yes, I've noticed the trend too :-( But that's a problem with the
> people using the tool, mostly, not with the tool itself.
With respect to at least one person in this category, I don't think that
their main original inspiration was checkpatch in the first place. More
random information collected from developer comments, that person's own
notion of what good code is, etc. So there may be limits to what one can
do to checkpatch that will have an impact on this issue.
Furthermore, probably people who use checkpatch in the right way, ie to
check their patches, don't actually mention their use of checkpatch. They
just fix up their commits and move on.
julia
Powered by blists - more mailing lists