From: Dave Airlie <airlied@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
tech-board-discuss@lists.linuxfoundation.org,
LKML <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH] CodingStyle: Inclusive Terminology
Date: Sun, 5 Jul 2020 09:34:57 +1000 [thread overview]
Message-ID: <CAPM=9txOgRYc7RM3fzohB4=Ejcp_xMGLBX_OOCOD=r+W6D678A@mail.gmail.com> (raw)
In-Reply-To: <20200705064348.71d4d51f@canb.auug.org.au>
On Sun, 5 Jul 2020 at 06:45, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Dan,
>
> On Sat, 04 Jul 2020 13:02:51 -0700 Dan Williams <dan.j.williams@intel.com> wrote:
> >
> > +Linux kernel inclusive terminology
> > +==================================
> > +
> > +The Linux kernel is a global software project, and in 2020 there was a
> > +global reckoning on race relations that caused many organizations to
> > +re-evaluate their policies and practices relative to the inclusion of
> > +people of African descent. This document describes why the 'Naming'
>
> I feel a need to point out that racial issues are wider than just
> people of African descent ... Also, others have pointed out that
> slavery is not just restricted to those of African descent.
The racial issues are wider than that, and even wider again I'm sure,
but in 2020 this is as good a place to start as any, and the trigger
as that sentence says was in 2020, there was a reckoning about it
mainly due to people of African descent. That trigger has had flow on
effects in other countries, but I'm not sure that sentence in any way
diminishes that, it's merely an introduction to why this change is
happening now.
As for the non-black slavery, others have never pointed this out
before in 30 years of master/slave terminology? surely if white
slavery was as big a problem, they be as supportive of this, even more
so. It speaks volumes that I've never heard white slavery as a problem
once in 30 years, but now I'm hearing about it a few times, and
somehow as an excuse not to support this.
Dave.
_______________________________________________
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-04 23:35 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 20:02 Dan Williams
2020-07-04 20:31 ` Randy Dunlap
2020-07-04 23:41 ` Dave Airlie
2020-07-05 0:10 ` Matthew Wilcox
2020-07-05 1:10 ` [Ksummit-discuss] [Tech-board-discuss] " Kees Cook
2020-07-05 2:44 ` Randy Dunlap
2020-07-06 11:15 ` Michael Kerrisk (man-pages)
2020-07-06 15:53 ` Kees Cook
2020-07-05 2:54 ` [Ksummit-discuss] " Dave Airlie
2020-07-04 20:44 ` Stephen Rothwell
2020-07-04 23:34 ` Dave Airlie [this message]
2020-07-05 2:12 ` Stephen Rothwell
2020-07-05 2:56 ` Dave Airlie
2020-07-05 3:23 ` James Bottomley
2020-07-05 3:26 ` Stephen Rothwell
2020-07-04 21:14 ` Olof Johansson
2020-07-04 21:25 ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-07-04 21:51 ` Joe Perches
2020-07-04 23:39 ` Dave Airlie
2020-07-05 0:08 ` Joe Perches
2020-07-05 1:32 ` Kees Cook
2020-07-05 17:50 ` opal hart
2020-07-04 23:42 ` [Ksummit-discuss] " Dave Airlie
2020-07-05 0:12 ` Matthew Wilcox
2020-07-06 7:06 ` NeilBrown
2020-07-06 7:10 ` NeilBrown
2020-07-06 7:22 ` Greg Kroah-Hartman
2020-07-06 7:53 ` Geert Uytterhoeven
2020-07-06 10:22 ` Greg Kroah-Hartman
2020-07-06 12:51 ` Matthew Wilcox
2020-07-06 12:59 ` Joe Perches
2020-07-06 13:04 ` Matthew Wilcox
2020-07-06 13:30 ` Joe Perches
2020-07-09 11:11 ` Mauro Carvalho Chehab
2020-07-13 4:25 ` Vinod Koul
2020-07-13 15:55 ` Dan Williams
2020-07-05 0:41 ` Kees Cook
2020-07-07 4:30 ` Dan Williams
2020-07-10 16:52 ` Andy Lutomirski
2020-07-05 4:55 ` Willy Tarreau
2020-07-06 3:13 ` Daniel Palmer
2020-07-06 12:45 ` Chris Mason via Ksummit-discuss
2020-07-06 14:06 ` Laurent Pinchart
2020-07-06 15:55 ` Chris Mason via Ksummit-discuss
2020-07-06 16:06 ` Mike Rapoport
2020-07-07 4:17 ` Dan Williams
2020-07-06 15:22 ` Arvind Sankar
2020-07-06 15:40 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-06 13:23 ` [Ksummit-discuss] " Tibor Raschko
2020-07-06 16:29 ` Andy Lutomirski
2020-07-07 4:00 ` Dan Williams
2020-07-07 5:56 ` Kees Cook
2020-07-07 6:49 ` Mike Rapoport
2020-07-07 13:37 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-07 15:24 ` Bird, Tim
2020-07-07 15:33 ` Randy Dunlap
2020-07-07 15:41 ` Steven Rostedt
2020-07-07 15:55 ` Bird, Tim
2020-07-07 6:56 ` [Ksummit-discuss] " Harrosh, Boaz
2020-07-07 8:54 ` Kees Cook
2020-07-07 13:41 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-07 14:45 ` Mike Rapoport
2020-07-07 20:56 ` Kees Cook
2020-07-07 21:48 ` [Ksummit-discuss] " Arvind Sankar
2020-07-07 12:13 ` Mark Brown
2020-07-06 18:30 ` [Ksummit-discuss] [Tech-board-discuss] " Shuah Khan
2020-07-06 23:58 ` Tibor Raschko
[not found] ` <20200709124327.369781a0@coco.lan>
2020-07-09 16:01 ` Shuah Khan
2020-07-09 16:13 ` Mark Brown
2020-07-09 16:32 ` James Bottomley
2020-07-09 16:35 ` Steven Rostedt
2020-07-07 4:04 ` Dan Williams
2020-07-06 19:15 ` Mark Brown
2020-07-07 0:48 ` Tibor Raschko
2020-07-07 21:26 ` Arvind Sankar
2020-07-07 23:54 ` Tibor Raschko
2020-07-07 4:08 ` Dan Williams
2020-07-07 9:36 ` Mark Brown
2020-07-06 21:31 ` [Ksummit-discuss] " Pavel Begunkov
2020-07-06 22:10 ` [Ksummit-discuss] [Tech-board-discuss] " Steven Rostedt
2020-07-06 22:17 ` Pavel Begunkov
2020-07-06 22:28 ` Steven Rostedt
2020-07-06 23:03 ` Pavel Begunkov
2020-07-08 3:42 ` Stephen Hemminger
2020-07-07 6:56 ` [Ksummit-discuss] " SeongJae Park via Ksummit-discuss
2020-07-08 7:12 ` Dan Williams
2020-07-08 9:28 ` SeongJae Park via Ksummit-discuss
2020-07-07 7:51 ` Christian Brauner
2020-07-17 8:35 ` Pavel Machek
2020-07-26 15:30 ` Laurent Pinchart
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='CAPM=9txOgRYc7RM3fzohB4=Ejcp_xMGLBX_OOCOD=r+W6D678A@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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