Commit 5075edae authored by Minjune Kim's avatar Minjune Kim Committed by Marcel Holtmann

Bluetooth: btusb: Correct typos based on checkpatch.pl

Signed-off-by: default avatarMinjune Kim <infinite.minjune.kim@gmail.com>
Signed-off-by: default avatarMarcel Holtmann <marcel@holtmann.org>
parent ff289559
...@@ -1581,7 +1581,7 @@ static int btusb_setup_intel(struct hci_dev *hdev) ...@@ -1581,7 +1581,7 @@ static int btusb_setup_intel(struct hci_dev *hdev)
/* fw_patch_num indicates the version of patch the device currently /* fw_patch_num indicates the version of patch the device currently
* have. If there is no patch data in the device, it is always 0x00. * have. If there is no patch data in the device, it is always 0x00.
* So, if it is other than 0x00, no need to patch the deivce again. * So, if it is other than 0x00, no need to patch the device again.
*/ */
if (ver->fw_patch_num) { if (ver->fw_patch_num) {
BT_INFO("%s: Intel device is already patched. patch num: %02x", BT_INFO("%s: Intel device is already patched. patch num: %02x",
...@@ -2100,7 +2100,7 @@ static int btusb_setup_intel_new(struct hci_dev *hdev) ...@@ -2100,7 +2100,7 @@ static int btusb_setup_intel_new(struct hci_dev *hdev)
frag_len += sizeof(*cmd) + cmd->plen; frag_len += sizeof(*cmd) + cmd->plen;
/* The paramter length of the secure send command requires /* The parameter length of the secure send command requires
* a 4 byte alignment. It happens so that the firmware file * a 4 byte alignment. It happens so that the firmware file
* contains proper Intel_NOP commands to align the fragments * contains proper Intel_NOP commands to align the fragments
* as needed. * as needed.
......
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