Skip to content

Commit

Permalink
Bluetooth: mgmt: fix typos
Browse files Browse the repository at this point in the history
A few comments had minor typos. These are being fixed.

Signed-off-by: Florian Grandel <fgrandel@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
  • Loading branch information
Florian Grandel authored and Marcel Holtmann committed May 26, 2015
1 parent 04b8c81 commit f72186d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions net/bluetooth/mgmt.c
Original file line number Diff line number Diff line change
Expand Up @@ -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.
*
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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.
*
Expand Down

0 comments on commit f72186d

Please sign in to comment.