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
Subject: Re: [PATCH] improve the kernel quality and reduce the amount of BS patches
Date: Thu, 18 Aug 2022 01:48:21 -0400 [thread overview]
Message-ID: <cf4ee22c2bcfa00c7ae8f19c1ae8800f789a4f7f.camel@perches.com> (raw)
In-Reply-To: <YvxNvpF7n1VqNnbD@ZenIV>
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
next prev parent reply other threads:[~2022-08-18 5:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 1:35 [PATCH] drivers: char: mem: changed 'unsigned' to 'unsigned int' Paul Lemmermann
2022-08-17 2:09 ` [PATCH] improve the kernel quality and reduce the amount of BS patches Al Viro
2022-08-17 2:18 ` Al Viro
2022-08-17 2:29 ` Randy Dunlap
2022-08-18 5:48 ` Joe Perches [this message]
2022-08-18 14:52 ` [PATCH] drivers: char: mem: changed 'unsigned' to 'unsigned int' Greg KH
2022-08-19 1:52 ` Paul Lemmermann
2022-08-21 8:35 ` Greg KH
2022-08-21 15:49 ` ThePaulODoom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf4ee22c2bcfa00c7ae8f19c1ae8800f789a4f7f.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thepaulodoom@thepaulodoom.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®