Thread (21 messages) 21 messages, 3 authors, 2021-05-31

Re: [PATCH 06/12] Bluetooth: use inclusive language in RFCOMM

From: Archie Pusaka <hidden>
Date: 2021-05-31 08:44:45
Also in: linux-bluetooth, lkml

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 [off-list ref] wrote:
Hi Archie,
quoted
Use "central" and "peripheral".

Signed-off-by: Archie Pusaka <redacted>
Reviewed-by: Miao-chen Chou <redacted>

---

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help