Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <1510852186.31559.37.camel@perches.com>
Subject: Re: [PATCH 1/7] checkpatch: Implement new --ignore-cfg parameter
From:   Joe Perches <joe@perches.com>
To:     Knut Omang <knut.omang@oracle.com>, linux-kernel@vger.kernel.org
Cc:     Andy Whitcroft <apw@canonical.com>,
        Andrew Morton <akpm@linux-foundation.org>
Date:   Thu, 16 Nov 2017 09:09:46 -0800
In-Reply-To: <280c16fb1b8a645f0c62cea03f440fd0661af898.1510840787.git-series.knut.omang@oracle.com>
References: <cover.3dd1d0c1f15a7a7c418f20ebafc9719afc1c2704.1510840787.git-series.knut.omang@oracle.com>
         <280c16fb1b8a645f0c62cea03f440fd0661af898.1510840787.git-series.knut.omang@oracle.com>
Content-Type: text/plain; charset="ISO-8859-1"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

(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?

From 1584259533694640943@xxx Thu Nov 16 21:27:07 +0000 2017
X-GM-THRID: 1584246136620373906
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread