linux-kernel - Re: [PATCH] Bluetooth: L2CAP: Rudimentary typo fixes

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]

Date:   Thu, 25 Mar 2021 10:20:56 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>, marcel@...tmann.org,
        johan.hedberg@...il.com, luiz.dentz@...il.com, davem@...emloft.net,
        kuba@...nel.org, linux-bluetooth@...r.kernel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: Rudimentary typo fixes

On 3/24/21 9:35 PM, Bhaskar Chowdhury wrote:
> 
> s/minium/minimum/
> s/procdure/procedure/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>

Acked-by: Randy Dunlap <rdunlap@...radead.org>

> ---
>  net/bluetooth/l2cap_core.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 72c2f5226d67..b38e80a0e819 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -1690,7 +1690,7 @@ static void l2cap_le_conn_ready(struct l2cap_conn *conn)
>  		smp_conn_security(hcon, hcon->pending_sec_level);
> 
>  	/* For LE slave connections, make sure the connection interval
> -	 * is in the range of the minium and maximum interval that has
> +	 * is in the range of the minimum and maximum interval that has
>  	 * been configured for this connection. If not, then trigger
>  	 * the connection update procedure.
>  	 */
> @@ -7542,7 +7542,7 @@ static void l2cap_data_channel(struct l2cap_conn *conn, u16 cid,
>  	BT_DBG("chan %p, len %d", chan, skb->len);
> 
>  	/* If we receive data on a fixed channel before the info req/rsp
> -	 * procdure is done simply assume that the channel is supported
> +	 * procedure is done simply assume that the channel is supported
>  	 * and mark it as ready.
>  	 */
>  	if (chan->chan_type == L2CAP_CHAN_FIXED)
> --


-- 
~Randy