[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf4ee22c2bcfa00c7ae8f19c1ae8800f789a4f7f.camel@perches.com>
Date: Thu, 18 Aug 2022 01:48:21 -0400
From: Joe Perches <joe@...ches.com>
To: Al Viro <viro@...iv.linux.org.uk>,
Paul Lemmermann <thepaulodoom@...paulodoom.com>
Cc: arnd@...db.de, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] improve the kernel quality and reduce the amount of BS
patches
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
Powered by blists - more mailing lists