[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJQfnxHf1FEe-TWgSj7rJ=h4+_=LXm0QPXHoJUn3tpWnm6mvtw@mail.gmail.com>
Date: Mon, 31 May 2021 16:44:25 +0800
From: Archie Pusaka <apusaka@...gle.com>
To: Marcel Holtmann <marcel@...tmann.org>
Cc: linux-bluetooth <linux-bluetooth@...r.kernel.org>,
CrosBT Upstreaming <chromeos-bluetooth-upstreaming@...omium.org>,
Archie Pusaka <apusaka@...omium.org>,
Miao-chen Chou <mcchou@...omium.org>,
"David S. Miller" <davem@...emloft.net>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Johan Hedberg <johan.hedberg@...il.com>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
Matthieu Baerts <matthieu.baerts@...sares.net>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Stefan Schmidt <stefan@...enfreihafen.org>,
LKML <linux-kernel@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: Re: [PATCH 06/12] Bluetooth: use inclusive language in RFCOMM
Hi Marcel,
Thanks for the reply. I have sent v2 which omits this patch. Please take a look.
I am not familiar with the libbluetooth API. Could you tell me more about it?
Beside this and the L2CAP change, are there any other terms
replacement which can't be accepted due to the libbluetooth API?
Cheers,
Archie
On Wed, 26 May 2021 at 23:07, Marcel Holtmann <marcel@...tmann.org> wrote:
>
> Hi Archie,
>
> > Use "central" and "peripheral".
> >
> > Signed-off-by: Archie Pusaka <apusaka@...omium.org>
> > Reviewed-by: Miao-chen Chou <mcchou@...omium.org>
> >
> > ---
> >
> > include/net/bluetooth/rfcomm.h | 2 +-
> > net/bluetooth/rfcomm/sock.c | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/net/bluetooth/rfcomm.h b/include/net/bluetooth/rfcomm.h
> > index 99d26879b02a..6472ec0053b9 100644
> > --- a/include/net/bluetooth/rfcomm.h
> > +++ b/include/net/bluetooth/rfcomm.h
> > @@ -290,7 +290,7 @@ struct rfcomm_conninfo {
> > };
> >
> > #define RFCOMM_LM 0x03
> > -#define RFCOMM_LM_MASTER 0x0001
> > +#define RFCOMM_LM_CENTRAL 0x0001
> > #define RFCOMM_LM_AUTH 0x0002
> > #define RFCOMM_LM_ENCRYPT 0x0004
> > #define RFCOMM_LM_TRUSTED 0x0008
>
> I am not planning to accept this change any time soon since this is also in the libbluetooth API.
>
> Regards
>
> Marcel
>
Powered by blists - more mailing lists