[PATCH] Bluetooth: L2CAP: Rudimentary typo fixes

[PATCH] Bluetooth: L2CAP: Rudimentary typo fixes

[Bhaskar Chowdhury]

s/minium/minimum/
s/procdure/procedure/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
 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)
--
2.30.1

Re: [PATCH] Bluetooth: L2CAP: Rudimentary typo fixes

[Randy Dunlap]

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

Acked-by: Randy Dunlap <rdunlap@infradead.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

Re: [PATCH] Bluetooth: L2CAP: Rudimentary typo fixes

[Marcel Holtmann]

Hi Bhaskar,

> s/minium/minimum/
> s/procdure/procedure/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> net/bluetooth/l2cap_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)

patch has been applied to bluetooth-next tree.

Regards

Marcel