Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <cf4ee22c2bcfa00c7ae8f19c1ae8800f789a4f7f.camel@perches.com>
Subject: Re: [PATCH] improve the kernel quality and reduce the amount of BS
 patches
From:   Joe Perches <joe@perches.com>
To:     Al Viro <viro@zeniv.linux.org.uk>,
        Paul Lemmermann <thepaulodoom@thepaulodoom.com>
Cc:     arnd@arndb.de, gregkh@linuxfoundation.org,
        linux-kernel@vger.kernel.org
Date:   Thu, 18 Aug 2022 01:48:21 -0400
In-Reply-To: <YvxNvpF7n1VqNnbD@ZenIV>
References: <YvxF0yn07ztg9r4A@gus-fring.localdomain>
         <YvxNvpF7n1VqNnbD@ZenIV>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8BIT
User-Agent: Evolution 3.44.4 (3.44.4-1.fc36) 
MIME-Version: 1.0
Precedence: bulk

On Wed, 2022-08-17 at 03:09 +0100, Al Viro wrote:
> this idiocy has gone too far    

Al's semi-annual post?

From 2015:

https://lore.kernel.org/all/bb0fd4fc28b844ac9b63a58c9ffd24a88f7f78cc.1473875340.git.joe@perches.com/

checkpatch can be a useful tool for patches.

It can be a much more controversial tool when used on files with the
-f option for style and whitespace changes for code that is relatively
stable, obsolete, or for maintained by specific individuals.

o By default, allow checkpatch to be used with the -f|--file option
  for files in drivers/staging/
o Add an undocumented --force command line option to be used together
  with the -f|--file option to scan any file