Bluetooth: L2CAP: Rudimentary typo fixes

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

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
index 56e1975cdef19a30b631042393bff0131b630cb8..7641fdfb26280d1ce2d1c3be3d361436131ba843 100644 (file)
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@ -1694,7 +1694,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.
         */
@@ -7552,7 +7552,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)