From: Archie Pusaka <apusaka@google.com>
To: Emil Lenngren <emil.lenngren@gmail.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
"Marcel Holtmann" <marcel@holtmann.org>,
"CrosBT Upstreaming"
<chromeos-bluetooth-upstreaming@chromium.org>,
"Archie Pusaka" <apusaka@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
"Matthieu Baerts" <matthieu.baerts@tessares.net>,
"Miao-chen Chou" <mcchou@chromium.org>,
"Ole Bjørn Midtbø" <omidtbo@cisco.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Stefan Schmidt" <stefan@datenfreihafen.org>,
LKML <linux-kernel@vger.kernel.org>,
"Network Development" <netdev@vger.kernel.org>
Subject: Re: [PATCH 00/12] Bluetooth: use inclusive language
Date: Tue, 25 May 2021 22:34:07 +0800 [thread overview]
Message-ID: <CAJQfnxG1Q=6n4H_kTbFA-=b0Rbs6v7WE8mKKonqvw-nXhLnLMA@mail.gmail.com> (raw)
In-Reply-To: <CAO1O6sehBfi+Tn6EEC8XgoORrD=JF9zO9tDCbJBgL=JpaBdL2w@mail.gmail.com>
Hi Emil,
On Tue, 25 May 2021 at 20:19, Emil Lenngren <emil.lenngren@gmail.com> wrote:
>
> Hi Archie,
>
> Den tis 25 maj 2021 kl 12:46 skrev Archie Pusaka <apusaka@google.com>:
> >
> > From: Archie Pusaka <apusaka@chromium.org>
> >
> > Hi linux-bluetooth maintainers,
> >
> > This series contains inclusive language patches, to promote usage of
> > central, peripheral, reject list, and accept list. I tried to divide
> > the change to several smaller patches to ease downstreamers to make
> > gradual change.
> >
> > There are still three occurences in debugfs (patch 09/12) in which the
> > original less inclusive terms is still left as-is since it is a
> > file name, and I afraid replacing them will cause instability to
> > other systems depending on that file name.
> >
> >
> > Archie Pusaka (12):
> > Bluetooth: use inclusive language in HCI role
> > Bluetooth: use inclusive language in hci_core.h
> > Bluetooth: use inclusive language to describe CPB
> > Bluetooth: use inclusive language in HCI LE features
> > Bluetooth: use inclusive language in L2CAP
> > Bluetooth: use inclusive language in RFCOMM
> > Bluetooth: use inclusive language when tracking connections
> > Bluetooth: use inclusive language in SMP
> > Bluetooth: use inclusive language in debugfs
> > Bluetooth: use inclusive language when filtering devices out
> > Bluetooth: use inclusive language when filtering devices in
> > Bluetooth: use inclusive language in comments
> >
> > include/net/bluetooth/hci.h | 98 +++++++++++++-------------
> > include/net/bluetooth/hci_core.h | 22 +++---
> > include/net/bluetooth/l2cap.h | 2 +-
> > include/net/bluetooth/mgmt.h | 2 +-
> > include/net/bluetooth/rfcomm.h | 2 +-
> > net/bluetooth/amp.c | 2 +-
> > net/bluetooth/hci_conn.c | 32 ++++-----
> > net/bluetooth/hci_core.c | 46 ++++++-------
> > net/bluetooth/hci_debugfs.c | 20 +++---
> > net/bluetooth/hci_event.c | 114 +++++++++++++++----------------
> > net/bluetooth/hci_request.c | 106 ++++++++++++++--------------
> > net/bluetooth/hci_sock.c | 12 ++--
> > net/bluetooth/hidp/core.c | 2 +-
> > net/bluetooth/l2cap_core.c | 16 ++---
> > net/bluetooth/l2cap_sock.c | 4 +-
> > net/bluetooth/mgmt.c | 36 +++++-----
> > net/bluetooth/rfcomm/sock.c | 4 +-
> > net/bluetooth/smp.c | 86 +++++++++++------------
> > net/bluetooth/smp.h | 6 +-
> > 19 files changed, 309 insertions(+), 303 deletions(-)
> >
> > --
> > 2.31.1.818.g46aad6cb9e-goog
> >
>
> Interesting move and good initiative!
>
> In my opinion however, shouldn't we wait until Bluetooth SIG changes
> the naming in the specification itself first (or rather push them to
> make the changes in the first place)? If they are about to change
> names, it would be good to make sure we end up with the same word
> choices so that we don't call one thing "le peripheral initiated
> feature exchange" while the standard calls it "le follower initiated
> feature exchange" or similar. Using different terminology than what's
> specified by the standard could easily end up in confusion I guess,
> and even more if different stacks invented their own alternative
> terminology.
So far the Bluetooth SIG has only published an "Appropriate Language
Mapping Table" (https://specificationrefs.bluetooth.com/language-mapping/Appropriate_Language_Mapping_Table.pdf).
It doesn't look like it's finalized, but it's enough to get started.
Hopefully someone in the community can help to push the changes to the
spec?
> In any case, I'm for example not sure if central/peripheral are the
> best words to use, since those are tied to a specific higher level
> profile (Generic Access Profile) and those words are not mentioned at
> all in the spec outside that context. The SMP chapter for example uses
> the terminology "initiator" and "responder", so maybe those are better
> word choices, at least in SMP.
Thanks, you are correct about that. I didn't read the spec thoroughly
and just did a simple replacement. I shall incorporate your suggestion
if this set of patches is greenlighted.
Cheers,
Archie
next prev parent reply other threads:[~2021-05-25 14:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 10:29 [PATCH 00/12] Bluetooth: use inclusive language Archie Pusaka
2021-05-25 10:29 ` [PATCH 01/12] Bluetooth: use inclusive language in HCI role Archie Pusaka
2021-05-25 10:29 ` [PATCH 02/12] Bluetooth: use inclusive language in hci_core.h Archie Pusaka
2021-05-25 10:29 ` [PATCH 03/12] Bluetooth: use inclusive language to describe CPB Archie Pusaka
2021-05-25 10:29 ` [PATCH 04/12] Bluetooth: use inclusive language in HCI LE features Archie Pusaka
2021-05-25 10:29 ` [PATCH 05/12] Bluetooth: use inclusive language in L2CAP Archie Pusaka
2021-05-26 15:12 ` Marcel Holtmann
2021-05-25 10:29 ` [PATCH 06/12] Bluetooth: use inclusive language in RFCOMM Archie Pusaka
2021-05-26 15:07 ` Marcel Holtmann
2021-05-31 8:44 ` Archie Pusaka
2021-05-25 10:29 ` [PATCH 07/12] Bluetooth: use inclusive language when tracking connections Archie Pusaka
2021-05-25 10:29 ` [PATCH 08/12] Bluetooth: use inclusive language in SMP Archie Pusaka
2021-05-25 10:29 ` [PATCH 09/12] Bluetooth: use inclusive language in debugfs Archie Pusaka
2021-05-26 15:09 ` Marcel Holtmann
2021-05-25 10:29 ` [PATCH 10/12] Bluetooth: use inclusive language when filtering devices out Archie Pusaka
2021-05-26 15:11 ` Marcel Holtmann
2021-05-25 10:29 ` [PATCH 11/12] Bluetooth: use inclusive language when filtering devices in Archie Pusaka
2021-05-25 10:29 ` [PATCH 12/12] Bluetooth: use inclusive language in comments Archie Pusaka
2021-05-25 12:18 ` [PATCH 00/12] Bluetooth: use inclusive language Emil Lenngren
2021-05-25 14:34 ` Archie Pusaka [this message]
2021-05-25 15:17 ` Emil Lenngren
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='CAJQfnxG1Q=6n4H_kTbFA-=b0Rbs6v7WE8mKKonqvw-nXhLnLMA@mail.gmail.com' \
--to=apusaka@google.com \
--cc=apusaka@chromium.org \
--cc=bigeasy@linutronix.de \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--cc=emil.lenngren@gmail.com \
--cc=gustavoars@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=matthieu.baerts@tessares.net \
--cc=mcchou@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=omidtbo@cisco.com \
--cc=stefan@datenfreihafen.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).