iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bluetooth: btusb: Correct typos based on checkpatch.pl

Browse Source 
Signed-off-by: Minjune Kim <infinite.minjune.kim@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
Minjune Kim 2015-08-27 13:21:52 +09:00 committed by Marcel Holtmann
parent ff2895592f
commit 5075edae08
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
drivers/bluetooth/btusb.c
View File

@ -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)
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.