From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Date: Thu, 22 Sep 2016 17:50:44 +0000 Subject: Re: "CodingStyle: Clarify and complete chapter 7" in docs-next Message-Id: <1474566644.8253.15.camel@perches.com> List-Id: References: <20160920001159.GM2356@ZenIV.linux.org.uk> <1474339566.1954.25.camel@perches.com> <1474353123.1954.28.camel@perches.com> <20160922112407.47da9393@endymion> <1474540930.8253.9.camel@perches.com> <20160922135758.0399725d@endymion> <20160922131103.GW2356@ZenIV.linux.org.uk> In-Reply-To: <20160922131103.GW2356@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Al Viro , Jean Delvare Cc: Julia Lawall , Ilya Dryomov , Andy Whitcroft , Linus Torvalds , Jonathan Corbet , Ceph Development , Alex Elder , Sage Weil , LKML , kernel-janitors@vger.kernel.org, Andrew Morton , linux-doc@vger.kernel.org On Thu, 2016-09-22 at 14:11 +0100, Al Viro wrote: > The main intent of checkpatch these days appears to be providing an easy > way of thoughtless inflation of commit counts, everything else be damned. You've made this statement several times over many years. I don't believe it's true. I doubt anyone is getting paid per commit. Who really cares enough to game some stupid little metric? If it's really a big deal, name some names. =A0Otherwise please stop with this dubious argument/point. > Some of these checks are common-sense, some are > absolutely arbitrary, Essentially all of the checkpatch rules are arbitrary. The compiler doesn't care one way or another. All the checks exist just to make code appear more consistent. The conceit being that more consistent code is easier for humans to read and spot potential defects and possible reuse patterns. -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html