[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <12122F14-688A-41B0-ABA7-90CC893005E8@holtmann.org>
Date: Tue, 15 Jun 2021 15:43:54 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: 13145886936@....com
Cc: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Bluez mailing list <linux-bluetooth@...r.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
gushengxian <gushengxian@...ong.com>
Subject: Re: [PATCH] Bluetooth: Fix a spelling mistake
Hi,
> Fix a spelling mistake.
>
> Signed-off-by: gushengxian <gushengxian@...ong.com>
> ---
> net/bluetooth/hci_conn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
> index 2b5059a56cda..e91ac6945ec3 100644
> --- a/net/bluetooth/hci_conn.c
> +++ b/net/bluetooth/hci_conn.c
> @@ -760,7 +760,7 @@ void hci_le_conn_failed(struct hci_conn *conn, u8 status)
> /* If the status indicates successful cancellation of
> * the attempt (i.e. Unknown Connection Id) there's no point of
> * notifying failure since we'll go back to keep trying to
> - * connect. The only exception is explicit connect requests
> + * connect. The only exception is explicit connection requests
> * where a timeout + cancel does indicate an actual failure.
I am not even convinced this is a spelling mistake since according to the specification they are connect requests. Anyhow, I no considering patches without proper real name attached to it and send from a total vague email address.
Regards
Marcel
Powered by blists - more mailing lists