2021-03-25 04:38:14

by Bhaskar Chowdhury

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

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

Signed-off-by: Bhaskar Chowdhury <[email protected]>
---
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

2021-03-25 17:23:09

by Randy Dunlap

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 <[email protected]>

Acked-by: Randy Dunlap <[email protected]>

> ---
> 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