|
@@ -7577,7 +7577,7 @@ void mgmt_new_ltk(struct hci_dev *hdev, struct smp_ltk *key, bool persistent)
|
|
|
memset(&ev, 0, sizeof(ev));
|
|
|
|
|
|
/* 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
|
|
|
* next time around.
|
|
|
*
|
|
@@ -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
|
|
|
* using a public address or static random address, do not
|
|
|
* 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.
|
|
|
*
|
|
|
* 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,
|
|
|
memset(&ev, 0, sizeof(ev));
|
|
|
|
|
|
/* 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
|
|
|
* the next time around.
|
|
|
*
|