From: SeongJae Park <sjpark@amazon.com>
To: <akpm@linux-foundation.org>, <apw@canonical.com>, <joe@perches.com>
Cc: SeongJae Park <sjpark@amazon.de>, <colin.king@canonical.com>,
<sj38.park@gmail.com>, <jslaby@suse.cz>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v4 0/2] Recommend denylist/allowlist instead of blacklist/whitelist
Date: Thu, 11 Jun 2020 08:25:48 +0200 [thread overview]
Message-ID: <20200611062550.20113-1-sjpark@amazon.com> (raw)
From: SeongJae Park <sjpark@amazon.de>
This patchset 1) adds support of deprecated terms in the 'checkpatch.pl'
and 2) set the 'blacklist' and 'whitelist' as deprecated with
replacement suggestion of 'denylist' and 'allowlist', because the
suggestions are incontrovertible, doesn't make people hurt, and more
self-explanatory.
The patches are based on latest 'next/master'. You can get the complete
git tree at:
https://github.com/sjp38/linux/tree/patches/checkpatch/deprecate_blacklist_whitelist_on_next_v4
Patch History
=============
Changes from v3
(https://lore.kernel.org/lkml/20200610065223.29894-1-sjpark@amazon.com/)
- Reuse the file read code for 'spelling.txt' (Joe Perches)
- Suggest 'denylist' rather than 'blocklist' (Jiri Slaby)
- Rebased on today's next/master
Changes from v2
(https://lore.kernel.org/lkml/20200609122549.26304-1-sjpark@amazon.com/)
- Implement and use deprecated terms check
Changes from v1
(https://lore.kernel.org/lkml/20200609121843.24147-1-sjpark@amazon.com/)
- Remove unnecessary commit message
SeongJae Park (2):
checkpatch: support deprecated terms checking
scripts/deprecated_terms: Recommend denylist/allowlist instead of
blacklist/whitelist
scripts/checkpatch.pl | 60 +++++++++++++++++++++++++++---------
scripts/deprecated_terms.txt | 7 +++++
2 files changed, 52 insertions(+), 15 deletions(-)
create mode 100644 scripts/deprecated_terms.txt
--
2.17.1
next reply other threads:[~2020-06-11 6:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 6:25 SeongJae Park [this message]
2020-06-11 6:25 ` [PATCH v4 1/2] checkpatch: support deprecated terms checking SeongJae Park
2020-07-25 13:02 ` Michał Mirosław
2020-07-25 16:36 ` Joe Perches
2020-07-25 17:29 ` Joe Perches
2020-07-25 23:35 ` SeongJae Park
2020-07-26 4:27 ` Joe Perches
2020-07-26 7:18 ` SeongJae Park
2020-07-26 7:29 ` Joe Perches
2020-07-26 7:45 ` SeongJae Park
2020-07-26 14:50 ` Joe Perches
2020-07-26 15:36 ` SeongJae Park
2020-07-26 16:42 ` Joe Perches
2020-07-26 18:07 ` SeongJae Park
2020-07-26 20:33 ` Michał Mirosław
2020-07-27 6:54 ` SeongJae Park
2020-07-27 20:44 ` Andrew Morton
2020-07-27 20:49 ` Joe Perches
2020-07-28 6:22 ` SeongJae Park
2020-06-11 6:25 ` [PATCH v4 2/2] scripts/deprecated_terms: Recommend denylist/allowlist instead of blacklist/whitelist SeongJae Park
2020-06-11 6:35 ` [PATCH v4 0/2] " Joe Perches
2020-06-11 7:38 ` SeongJae Park
2020-06-11 8:16 ` Jiri Slaby
2020-06-11 8:30 ` SeongJae Park
2020-06-11 8:32 ` Jiri Slaby
2020-06-11 10:43 ` Joe Perches
2020-06-12 6:40 ` SeongJae Park
2020-06-12 7:05 ` Joe Perches
2020-06-12 14:40 ` Michael Ellerman
2020-06-14 21:29 ` Pavel Machek
2020-06-15 4:21 ` Jiri Slaby
2020-06-15 6:12 ` Pavel Machek
2020-06-15 6:46 ` SeongJae Park
2020-06-15 7:00 ` Joe Perches
2020-06-15 7:39 ` Pavel Machek
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=20200611062550.20113-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=colin.king@canonical.com \
--cc=joe@perches.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
/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®