From: Pavel Machek <pavel@denx.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
SeongJae Park <sjpark@amazon.de>,
linux-kernel@vger.kernel.org,
tech-board-discuss@lists.linuxfoundation.org,
Chris Mason <clm@fb.clm>, Dave Airlie <airlied@redhat.com>
Subject: Re: [Ksummit-discuss] [PATCH v2] CodingStyle: Inclusive Terminology
Date: Sat, 11 Jul 2020 15:30:52 +0200 [thread overview]
Message-ID: <20200711133052.GA6407@amd> (raw)
In-Reply-To: <159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 696 bytes --]
On Wed 2020-07-08 00:23:59, Dan Williams wrote:
> Linux maintains a coding-style and its own idiomatic set of terminology.
> Update the style guidelines to recommend replacements for the terms
> master/slave and blacklist/whitelist.
>
> +replacements for 'blacklist/whitelist' are: 'denylist/allowlist' or
> +'blocklist/passlist'.
I don't see what is "non inclusive" about blacklist and whitelist...
Plus, please grep kernel for actual usages. blocklist/denylist is
_not_ suitable replacement for kernel use of blacklist.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 186 bytes --]
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@denx.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
SeongJae Park <sjpark@amazon.de>,
linux-kernel@vger.kernel.org,
tech-board-discuss@lists.linuxfoundation.org,
Chris Mason <clm@fb.clm>, Dave Airlie <airlied@redhat.com>,
torvalds@linux-foundation.org
Subject: Re: [Tech-board-discuss] [PATCH v2] CodingStyle: Inclusive Terminology
Date: Sat, 11 Jul 2020 15:30:52 +0200 [thread overview]
Message-ID: <20200711133052.GA6407@amd> (raw)
In-Reply-To: <159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Wed 2020-07-08 00:23:59, Dan Williams wrote:
> Linux maintains a coding-style and its own idiomatic set of terminology.
> Update the style guidelines to recommend replacements for the terms
> master/slave and blacklist/whitelist.
>
> +replacements for 'blacklist/whitelist' are: 'denylist/allowlist' or
> +'blocklist/passlist'.
I don't see what is "non inclusive" about blacklist and whitelist...
Plus, please grep kernel for actual usages. blocklist/denylist is
_not_ suitable replacement for kernel use of blacklist.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@denx.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: corbet@lwn.net, Randy Dunlap <rdunlap@infradead.org>,
Dave Airlie <airlied@redhat.com>,
Kees Cook <keescook@chromium.org>,
SeongJae Park <sjpark@amazon.de>, Olof Johansson <olof@lixom.net>,
Chris Mason <clm@fb.clm>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
torvalds@linux-foundation.org,
tech-board-discuss@lists.linuxfoundation.org,
ksummit-discuss@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] CodingStyle: Inclusive Terminology
Date: Sat, 11 Jul 2020 15:30:52 +0200 [thread overview]
Message-ID: <20200711133052.GA6407@amd> (raw)
In-Reply-To: <159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Wed 2020-07-08 00:23:59, Dan Williams wrote:
> Linux maintains a coding-style and its own idiomatic set of terminology.
> Update the style guidelines to recommend replacements for the terms
> master/slave and blacklist/whitelist.
>
> +replacements for 'blacklist/whitelist' are: 'denylist/allowlist' or
> +'blocklist/passlist'.
I don't see what is "non inclusive" about blacklist and whitelist...
Plus, please grep kernel for actual usages. blocklist/denylist is
_not_ suitable replacement for kernel use of blacklist.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-07-11 13:31 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 7:23 [Ksummit-discuss] [PATCH v2] CodingStyle: Inclusive Terminology Dan Williams
2020-07-08 7:23 ` Dan Williams
2020-07-08 7:23 ` [Tech-board-discuss] " Dan Williams
2020-07-08 7:52 ` [Ksummit-discuss] " Dan Williams
2020-07-08 7:52 ` Dan Williams
2020-07-08 7:52 ` [Tech-board-discuss] " Dan Williams
2020-07-08 8:22 ` [Ksummit-discuss] " Kees Cook
2020-07-08 8:22 ` Kees Cook
2020-07-08 8:22 ` [Tech-board-discuss] " Kees Cook
2020-07-08 14:43 ` [Ksummit-discuss] " Dan Williams
2020-07-08 14:43 ` Dan Williams
2020-07-08 14:43 ` [Tech-board-discuss] " Dan Williams
2020-07-08 9:30 ` [Ksummit-discuss] " Mark Brown
2020-07-08 9:30 ` Mark Brown
2020-07-08 9:30 ` Mark Brown
2020-07-08 10:07 ` [Ksummit-discuss] " Dan Carpenter
2020-07-08 10:07 ` Dan Carpenter
2020-07-08 10:07 ` [Tech-board-discuss] " Dan Carpenter
2020-07-08 11:04 ` Joe Perches
2020-07-08 11:04 ` Joe Perches
2020-07-08 11:04 ` [Tech-board-discuss] " Joe Perches
2020-07-08 15:14 ` [Ksummit-discuss] " Dan Williams
2020-07-08 15:14 ` Dan Williams
2020-07-08 15:14 ` [Tech-board-discuss] " Dan Williams
2020-07-08 15:59 ` [Ksummit-discuss] " James Bottomley
2020-07-08 15:59 ` James Bottomley
2020-07-08 14:22 ` [Ksummit-discuss] " tytso
2020-07-08 14:22 ` tytso
2020-07-08 14:22 ` [Tech-board-discuss] " tytso
2020-07-08 16:23 ` [Ksummit-discuss] " Christian Brauner
2020-07-08 16:23 ` Christian Brauner
2020-07-08 16:23 ` [Tech-board-discuss] " Christian Brauner
2020-07-08 16:42 ` [Ksummit-discuss] [Tech-board-discuss] " Shuah Khan
2020-07-08 16:42 ` Shuah Khan
2020-07-08 16:42 ` Shuah Khan
2020-07-08 18:59 ` [Ksummit-discuss] " Stephen Hemminger
2020-07-08 18:59 ` Stephen Hemminger
2020-07-08 18:59 ` [Tech-board-discuss] " Stephen Hemminger
2020-07-10 16:02 ` Linus Walleij
2020-07-10 16:02 ` Linus Walleij
2020-07-10 16:02 ` [Tech-board-discuss] " Linus Walleij
2020-07-10 16:13 ` [Ksummit-discuss] " Dan Williams
2020-07-10 16:13 ` Dan Williams
2020-07-10 16:13 ` [Tech-board-discuss] " Dan Williams
2020-07-11 13:30 ` Pavel Machek [this message]
2020-07-11 13:30 ` Pavel Machek
2020-07-11 13:30 ` [Tech-board-discuss] " 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=20200711133052.GA6407@amd \
--to=pavel@denx.de \
--cc=airlied@redhat.com \
--cc=clm@fb.clm \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjpark@amazon.de \
--cc=tech-board-discuss@lists.linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.