From: Pavel Machek <pavel@ucw.cz>
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,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Dave Airlie <airlied@redhat.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology
Date: Fri, 17 Jul 2020 10:36:30 +0200 [thread overview]
Message-ID: <20200717083630.GE1027@bug> (raw)
In-Reply-To: <159423201991.2466245.8461410729774664077.stgit@dwillia2-desk3.amr.corp.intel.com>
On Wed 2020-07-08 11:14:27, 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.
>
> Link: http://lore.kernel.org/r/159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Dave Airlie <airlied@redhat.com>
> Acked-by: SeongJae Park <sjpark@amazon.de>
> Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
> Acked-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> Reviewed-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Chris Mason <clm@fb.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> Changes since v2 [1]:
> - Pick up missed sign-offs and acks from Jon, Shuah, and Christian
> (sorry about missing those earlier).
>
> - Reformat the replacement list to make it easier to read.
>
> - Add 'controller' as a suggested replacement (Kees and Mark)
>
> - Fix up the paired term for 'performer' to be 'director' (Kees)
>
> - Collect some new acks, reviewed-by's, and sign-offs for v2.
>
> - Fix up Chris's email
>
> [1]: http://lore.kernel.org/r/159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com
>
>
> Documentation/process/coding-style.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> +Recommended replacements for 'blacklist/whitelist' are: + 'denylist / allowlist' +
> 'blocklist / passlist' + +Exceptions for introducing new usage is to maintain a
> userspace ABI/API, +or when updating code for an existing (as of 2020) hardware or
> protocol +specification that mandates those terms. For new specifications +translate
> specification usage of the terminology to the kernel coding +standard where possible.
Please try to understand how "blacklist" is used in the kernel before suggesting replacements.
NAK.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
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@ucw.cz>
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,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Dave Airlie <airlied@redhat.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
torvalds@linux-foundation.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Tech-board-discuss] [PATCH v3] CodingStyle: Inclusive Terminology
Date: Fri, 17 Jul 2020 10:36:30 +0200 [thread overview]
Message-ID: <20200717083630.GE1027@bug> (raw)
In-Reply-To: <159423201991.2466245.8461410729774664077.stgit@dwillia2-desk3.amr.corp.intel.com>
On Wed 2020-07-08 11:14:27, 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.
>
> Link: http://lore.kernel.org/r/159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Dave Airlie <airlied@redhat.com>
> Acked-by: SeongJae Park <sjpark@amazon.de>
> Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
> Acked-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> Reviewed-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Chris Mason <clm@fb.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> Changes since v2 [1]:
> - Pick up missed sign-offs and acks from Jon, Shuah, and Christian
> (sorry about missing those earlier).
>
> - Reformat the replacement list to make it easier to read.
>
> - Add 'controller' as a suggested replacement (Kees and Mark)
>
> - Fix up the paired term for 'performer' to be 'director' (Kees)
>
> - Collect some new acks, reviewed-by's, and sign-offs for v2.
>
> - Fix up Chris's email
>
> [1]: http://lore.kernel.org/r/159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com
>
>
> Documentation/process/coding-style.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> +Recommended replacements for 'blacklist/whitelist' are: + 'denylist / allowlist' +
> 'blocklist / passlist' + +Exceptions for introducing new usage is to maintain a
> userspace ABI/API, +or when updating code for an existing (as of 2020) hardware or
> protocol +specification that mandates those terms. For new specifications +translate
> specification usage of the terminology to the kernel coding +standard where possible.
Please try to understand how "blacklist" is used in the kernel before suggesting replacements.
NAK.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Dan Williams <dan.j.williams@intel.com>
Cc: corbet@lwn.net, Randy Dunlap <rdunlap@infradead.org>,
Dave Airlie <airlied@redhat.com>,
SeongJae Park <sjpark@amazon.de>,
Christian Brauner <christian.brauner@ubuntu.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Mark Brown <broonie@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Shuah Khan <skhan@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Kees Cook <keescook@chromium.org>,
Olof Johansson <olof@lixom.net>, Chris Mason <clm@fb.com>,
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 v3] CodingStyle: Inclusive Terminology
Date: Fri, 17 Jul 2020 10:36:30 +0200 [thread overview]
Message-ID: <20200717083630.GE1027@bug> (raw)
In-Reply-To: <159423201991.2466245.8461410729774664077.stgit@dwillia2-desk3.amr.corp.intel.com>
On Wed 2020-07-08 11:14:27, 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.
>
> Link: http://lore.kernel.org/r/159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Dave Airlie <airlied@redhat.com>
> Acked-by: SeongJae Park <sjpark@amazon.de>
> Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
> Acked-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> Reviewed-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Chris Mason <clm@fb.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> Changes since v2 [1]:
> - Pick up missed sign-offs and acks from Jon, Shuah, and Christian
> (sorry about missing those earlier).
>
> - Reformat the replacement list to make it easier to read.
>
> - Add 'controller' as a suggested replacement (Kees and Mark)
>
> - Fix up the paired term for 'performer' to be 'director' (Kees)
>
> - Collect some new acks, reviewed-by's, and sign-offs for v2.
>
> - Fix up Chris's email
>
> [1]: http://lore.kernel.org/r/159419296487.2464622.863943877093636532.stgit@dwillia2-desk3.amr.corp.intel.com
>
>
> Documentation/process/coding-style.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> +Recommended replacements for 'blacklist/whitelist' are: + 'denylist / allowlist' +
> 'blocklist / passlist' + +Exceptions for introducing new usage is to maintain a
> userspace ABI/API, +or when updating code for an existing (as of 2020) hardware or
> protocol +specification that mandates those terms. For new specifications +translate
> specification usage of the terminology to the kernel coding +standard where possible.
Please try to understand how "blacklist" is used in the kernel before suggesting replacements.
NAK.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2020-07-17 8:36 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 18:14 [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology Dan Williams
2020-07-08 18:14 ` Dan Williams
2020-07-08 18:14 ` [Tech-board-discuss] " Dan Williams
2020-07-09 7:25 ` [Ksummit-discuss] " Daniel Vetter
2020-07-09 7:25 ` Daniel Vetter
2020-07-09 7:25 ` [Tech-board-discuss] " Daniel Vetter
2020-07-09 19:08 ` Dan Williams
2020-07-09 19:08 ` Dan Williams
2020-07-09 19:08 ` [Tech-board-discuss] " Dan Williams
2020-07-09 9:45 ` Matthias Brugger
2020-07-09 9:45 ` Matthias Brugger
2020-07-09 9:45 ` [Tech-board-discuss] " Matthias Brugger
2020-07-09 19:10 ` Dan Williams
2020-07-09 19:10 ` Dan Williams
2020-07-09 19:10 ` [Tech-board-discuss] " Dan Williams
2020-07-10 21:12 ` Andy Lutomirski
2020-07-10 21:12 ` Andy Lutomirski
2020-07-10 21:12 ` [Tech-board-discuss] " Andy Lutomirski
2020-07-10 21:46 ` Dan Williams
2020-07-10 21:46 ` Dan Williams
2020-07-10 21:46 ` [Tech-board-discuss] " Dan Williams
2020-07-10 21:13 ` Laura Abbott
2020-07-10 21:13 ` Laura Abbott
2020-07-10 21:13 ` [Tech-board-discuss] " Laura Abbott
2020-07-10 21:48 ` [Ksummit-discuss] " Dan Williams
2020-07-10 21:48 ` Dan Williams
2020-07-10 21:48 ` [Tech-board-discuss] " Dan Williams
2020-07-10 22:38 ` Gustavo A. R. Silva
2020-07-10 22:38 ` Gustavo A. R. Silva
2020-07-11 20:31 ` [Ksummit-discuss] " josh
2020-07-11 20:31 ` josh
2020-07-11 20:31 ` [Tech-board-discuss] " josh
2020-07-13 4:20 ` Vinod Koul
2020-07-13 4:20 ` Vinod Koul
2020-07-13 4:20 ` [Tech-board-discuss] " Vinod Koul
2020-07-13 7:49 ` Joerg Roedel
2020-07-13 7:49 ` Joerg Roedel
2020-07-13 7:49 ` [Tech-board-discuss] " Joerg Roedel
2020-07-13 8:02 ` Takashi Iwai
2020-07-13 8:02 ` Takashi Iwai
2020-07-13 8:02 ` [Tech-board-discuss] " Takashi Iwai
2020-07-13 8:43 ` Julia Lawall
2020-07-13 8:43 ` Julia Lawall
2020-07-13 8:43 ` [Tech-board-discuss] " Julia Lawall
2020-07-13 9:36 ` Takashi Iwai
2020-07-13 9:36 ` Takashi Iwai
2020-07-13 9:36 ` [Tech-board-discuss] " Takashi Iwai
2020-07-13 9:39 ` Julia Lawall
2020-07-13 9:39 ` Julia Lawall
2020-07-13 9:39 ` [Tech-board-discuss] " Julia Lawall
2020-07-13 9:44 ` Takashi Iwai
2020-07-13 9:44 ` Takashi Iwai
2020-07-13 9:44 ` [Tech-board-discuss] " Takashi Iwai
2020-07-13 9:38 ` Hillf Danton
2020-07-13 15:06 ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-07-13 15:06 ` [Tech-board-discuss] [Ksummit-discuss] " James Bottomley
2020-07-14 4:39 ` josh
2020-07-14 4:39 ` josh
2020-07-14 4:39 ` [Tech-board-discuss] " josh
2020-07-14 6:43 ` Takashi Iwai
2020-07-14 6:43 ` Takashi Iwai
2020-07-14 6:43 ` [Tech-board-discuss] " Takashi Iwai
2020-07-17 16:47 ` Andy Lutomirski
2020-07-17 16:47 ` Andy Lutomirski
2020-07-17 16:47 ` [Tech-board-discuss] " Andy Lutomirski
2020-07-15 12:19 ` Jani Nikula
2020-07-15 12:19 ` Jani Nikula
2020-07-15 12:19 ` [Tech-board-discuss] " Jani Nikula
2020-07-17 8:36 ` Pavel Machek [this message]
2020-07-17 8:36 ` Pavel Machek
2020-07-17 8:36 ` [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=20200717083630.GE1027@bug \
--to=pavel@ucw.cz \
--cc=James.Bottomley@HansenPartnership.com \
--cc=airlied@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=dan.carpenter@oracle.com \
--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.