Commit f72186d2 authored by Florian Grandel's avatar Florian Grandel Committed by Marcel Holtmann

Bluetooth: mgmt: fix typos

A few comments had minor typos. These are being fixed.
Signed-off-by: default avatarFlorian Grandel <fgrandel@gmail.com>
Signed-off-by: default avatarMarcel Holtmann <marcel@holtmann.org>
parent 04b8c814
...@@ -7577,7 +7577,7 @@ void mgmt_new_ltk(struct hci_dev *hdev, struct smp_ltk *key, bool persistent) ...@@ -7577,7 +7577,7 @@ void mgmt_new_ltk(struct hci_dev *hdev, struct smp_ltk *key, bool persistent)
memset(&ev, 0, sizeof(ev)); memset(&ev, 0, sizeof(ev));
/* Devices using resolvable or non-resolvable random addresses /* Devices using resolvable or non-resolvable random addresses
* without providing an indentity resolving key don't require * without providing an identity resolving key don't require
* to store long term keys. Their addresses will change the * to store long term keys. Their addresses will change the
* next time around. * next time around.
* *
...@@ -7617,7 +7617,7 @@ void mgmt_new_irk(struct hci_dev *hdev, struct smp_irk *irk) ...@@ -7617,7 +7617,7 @@ void mgmt_new_irk(struct hci_dev *hdev, struct smp_irk *irk)
/* For identity resolving keys from devices that are already /* For identity resolving keys from devices that are already
* using a public address or static random address, do not * using a public address or static random address, do not
* ask for storing this key. The identity resolving key really * ask for storing this key. The identity resolving key really
* is only mandatory for devices using resovlable random * is only mandatory for devices using resolvable random
* addresses. * addresses.
* *
* Storing all identity resolving keys has the downside that * Storing all identity resolving keys has the downside that
...@@ -7646,7 +7646,7 @@ void mgmt_new_csrk(struct hci_dev *hdev, struct smp_csrk *csrk, ...@@ -7646,7 +7646,7 @@ void mgmt_new_csrk(struct hci_dev *hdev, struct smp_csrk *csrk,
memset(&ev, 0, sizeof(ev)); memset(&ev, 0, sizeof(ev));
/* Devices using resolvable or non-resolvable random addresses /* Devices using resolvable or non-resolvable random addresses
* without providing an indentity resolving key don't require * without providing an identity resolving key don't require
* to store signature resolving keys. Their addresses will change * to store signature resolving keys. Their addresses will change
* the next time around. * the next time around.
* *
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment