From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: NeilBrown <neilb@suse.com>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tech-board-discuss@lists.linuxfoundation.org,
Chris Mason <clm@fb.clm>
Subject: Re: [Ksummit-discuss] [PATCH] CodingStyle: Inclusive Terminology
Date: Mon, 6 Jul 2020 12:22:54 +0200 [thread overview]
Message-ID: <20200706102254.GA10206@kroah.com> (raw)
In-Reply-To: <CAMuHMdWj2d5GF1ZkuhzQxg9teA51zjF0oQQPWcphzK=kJ6-x9Q@mail.gmail.com>
On Mon, Jul 06, 2020 at 09:53:55AM +0200, Geert Uytterhoeven wrote:
> On Mon, Jul 6, 2020 at 9:22 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > look at the USB spec for an example of these terms being used in this
> > way for many decades.
>
> And when does the "gadget" enter the show? ;-)
It doesn't, as the USB spec does not describe that in any reasonable way
for us to use when dealing with drivers for both "types" of devices. So
we came up with the word "gadget" on purpose to be able to talk about
those things in a specific manner.
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-06 10:22 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 20:02 [PATCH] CodingStyle: Inclusive Terminology Dan Williams
2020-07-04 20:31 ` Randy Dunlap
2020-07-04 23:41 ` [Ksummit-discuss] " Dave Airlie
[not found] ` <CAFhKne9MA_G-UsvBFfX-gZRcu9Gb7Xt7UxQ14MTppdU3X1VYdQ@mail.gmail.com>
2020-07-05 1:10 ` [Tech-board-discuss] " Kees Cook
2020-07-05 2:44 ` Randy Dunlap
2020-07-06 11:15 ` [Ksummit-discuss] [Tech-board-discuss] " 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
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 ` [Tech-board-discuss] " James Bottomley
2020-07-04 21:51 ` Joe Perches
2020-07-04 23:39 ` [Ksummit-discuss] " 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:41 ` Kees Cook
2020-07-07 4:30 ` Dan Williams
2020-07-10 16:52 ` [Ksummit-discuss] " Andy Lutomirski
2020-07-05 4:55 ` Willy Tarreau
2020-07-06 3:13 ` Daniel Palmer
2020-07-06 12:45 ` Chris Mason
2020-07-06 14:06 ` [Ksummit-discuss] " Laurent Pinchart
2020-07-06 15:55 ` Chris Mason
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 ` [Tech-board-discuss] " Steven Rostedt
[not found] ` <CAFhKne_ZVWVhZX5hNEbeGBfU6BMRN9JKQeTsVYOcMmEH1cd3xg@mail.gmail.com>
2020-07-06 7:06 ` [Ksummit-discuss] " 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 [this message]
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-06 13:23 ` Tibor Raschko
2020-07-06 16:29 ` [Ksummit-discuss] " 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 ` [Tech-board-discuss] " Steven Rostedt
2020-07-07 15:24 ` [Ksummit-discuss] [Tech-board-discuss] " 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 ` [Tech-board-discuss] " Steven Rostedt
2020-07-07 14:45 ` [Ksummit-discuss] [Tech-board-discuss] " 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 ` [Tech-board-discuss] " Shuah Khan
2020-07-06 23:58 ` Tibor Raschko
2020-07-09 10:43 ` [Ksummit-discuss] " Mauro Carvalho Chehab
2020-07-09 16:01 ` Shuah Khan
2020-07-09 16:13 ` [Tech-board-discuss] [Ksummit-discuss] " Mark Brown
2020-07-09 16:32 ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-07-09 16:35 ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-07-10 9:38 ` [Ksummit-discuss] [Tech-board-discuss] " Tibor Raschko
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 ` Pavel Begunkov
2020-07-06 22:10 ` [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 ` [Ksummit-discuss] " Stephen Hemminger
2020-07-08 10:51 ` Pavel Begunkov
2020-07-07 6:56 ` [Ksummit-discuss] " SeongJae Park
2020-07-08 7:12 ` Dan Williams
2020-07-08 9:28 ` SeongJae Park
2020-07-07 7:51 ` Christian Brauner
2020-07-08 18:40 ` Daniel Vetter
2020-07-17 8:35 ` Pavel Machek
2020-07-26 15:30 ` [Ksummit-discuss] " 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=20200706102254.GA10206@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=clm@fb.clm \
--cc=geert@linux-m68k.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--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).