From: Dan Williams <dan.j.williams@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
SeongJae Park <sjpark@amazon.de>,
"linux-kernel@vger.kernel.org" <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: Fri, 10 Jul 2020 09:13:17 -0700 [thread overview]
Message-ID: <CAPcyv4jxnayrq6FKVkR-hCedm-XARd-wuQpFjfGVBg6j5ow0xw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdax9wSFtYxyCu18bWwc5T1GqNx7EDVA6JN+Qu42hOCh_A@mail.gmail.com>
On Fri, Jul 10, 2020 at 9:03 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Wed, Jul 8, 2020 at 9:40 AM Dan Williams <dan.j.williams@intel.com> 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
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Acked-by: Randy Dunlap <rdunlap@infradead.org>
> > Acked-by: Dave Airlie <airlied@redhat.com>
> > Acked-by: Kees Cook <keescook@chromium.org>
> > Acked-by: SeongJae Park <sjpark@amazon.de>
> > Signed-off-by: Olof Johansson <olof@lixom.net>
> > Signed-off-by: Chris Mason <clm@fb.clm>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Thanks Linus.
>
> An interesting piece on the topic is Douglas R. Hofstadter's
> satirical "A Person paper On Purity in Language" from 1985,
> which is funny, witty, Jonathan Swift-like and at one point
> convinced me on the importance of proper language in
> my professional work.
> http://www.cs.virginia.edu/~evans/cs655/readings/purity.html
...and thanks for that laugh.
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-07-10 16:13 UTC|newest]
Thread overview: 16+ 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:52 ` Dan Williams
2020-07-08 8:22 ` Kees Cook
2020-07-08 14:43 ` Dan Williams
2020-07-08 9:30 ` [Ksummit-discuss] [Tech-board-discuss] " Mark Brown
2020-07-08 10:07 ` [Ksummit-discuss] " Dan Carpenter
2020-07-08 11:04 ` Joe Perches
2020-07-08 15:14 ` Dan Williams
2020-07-08 15:59 ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-07-08 14:22 ` [Ksummit-discuss] " tytso
2020-07-08 16:23 ` Christian Brauner
2020-07-08 16:42 ` [Ksummit-discuss] [Tech-board-discuss] " Shuah Khan
2020-07-08 18:59 ` [Ksummit-discuss] " Stephen Hemminger
2020-07-10 16:02 ` Linus Walleij
2020-07-10 16:13 ` Dan Williams [this message]
2020-07-11 13:30 ` 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=CAPcyv4jxnayrq6FKVkR-hCedm-XARd-wuQpFjfGVBg6j5ow0xw@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=airlied@redhat.com \
--cc=clm@fb.clm \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linus.walleij@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).