linux-kernel - Re: [PATCH 1/7] checkpatch: Implement new --ignore-cfg parameter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1510852186.31559.37.camel@perches.com>
Date:   Thu, 16 Nov 2017 09:09:46 -0800
From:   Joe Perches <joe@...ches.com>
To:     Knut Omang <knut.omang@...cle.com>, linux-kernel@...r.kernel.org
Cc:     Andy Whitcroft <apw@...onical.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/7] checkpatch: Implement new --ignore-cfg parameter

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