netdev - Re: [PATCH 05/12] Bluetooth: use inclusive language in L2CAP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <234F83C9-7D24-41A5-A6B4-7B9F515323C0@holtmann.org>
Date:   Wed, 26 May 2021 17:12:51 +0200
From:   Marcel Holtmann <marcel@...tmann.org>
To:     Archie Pusaka <apusaka@...gle.com>
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>,
        Jakub Kicinski <kuba@...nel.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Luiz Augusto von Dentz <luiz.dentz@...il.com>,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 05/12] Bluetooth: use inclusive language in L2CAP

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/l2cap.h | 2 +-
> net/bluetooth/l2cap_sock.c    | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index 3c4f550e5a8b..1f5ed6b163af 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -89,7 +89,7 @@ struct l2cap_conninfo {
> };
> 
> #define L2CAP_LM	0x03
> -#define L2CAP_LM_MASTER		0x0001
> +#define L2CAP_LM_CENTRAL	0x0001
> #define L2CAP_LM_AUTH		0x0002
> #define L2CAP_LM_ENCRYPT	0x0004
> #define L2CAP_LM_TRUSTED	0x0008

same as with the RFCOMM change, this is something I am not prepared to do right now since it touches API.

Regards

Marcel