From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935737AbdKPRKP (ORCPT ); Thu, 16 Nov 2017 12:10:15 -0500 Received: from smtprelay0190.hostedemail.com ([216.40.44.190]:41707 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S934929AbdKPRJu (ORCPT ); Thu, 16 Nov 2017 12:09:50 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::,RULES_HIT:41:355:379:541:599:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2393:2559:2562:2828:2840:3138:3139:3140:3141:3142:3352:3865:3866:3867:3868:3870:3871:3872:3874:4321:5007:6120:6691:10004:10400:10848:11232:11658:11914:12740:12760:12895:13069:13311:13357:13439:14096:14097:14659:21080:21324:21627:30012:30046:30054:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:2,LUA_SUMMARY:none X-HE-Tag: sleep60_1b5fc681c6c1c X-Filterd-Recvd-Size: 1805 Message-ID: <1510852186.31559.37.camel@perches.com> Subject: Re: [PATCH 1/7] checkpatch: Implement new --ignore-cfg parameter From: Joe Perches To: Knut Omang , linux-kernel@vger.kernel.org Cc: Andy Whitcroft , Andrew Morton Date: Thu, 16 Nov 2017 09:09:46 -0800 In-Reply-To: <280c16fb1b8a645f0c62cea03f440fd0661af898.1510840787.git-series.knut.omang@oracle.com> References: <280c16fb1b8a645f0c62cea03f440fd0661af898.1510840787.git-series.knut.omang@oracle.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.26.1-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (adding Andrew Morton) On Thu, 2017-11-16 at 18:01 +0100, Knut Omang wrote: > This parameter is intended to be used in a subsequent commit to kbuild to allow > a convenient way to run checkpatch from make. _why_ is this useful? > By accepting comments and multiple lines of commands, the idea is that the > maintainer or someone else with good knowledge of the code can maintain a file > per directory and group the different commands into commented sections that can > serve both as documentation of the current checkpatch status, a way to define > the line of tolerance (and gradually tighten it as fixes comes in) and as > documentation of TODOs and dont's if there are well justified exceptions. checkpatch can be run any time over individual files so I don't find this compelling. Does anyone else?