Bluetooth: btusb: Correct typos based on checkpatch.pl
authorMinjune Kim <infinite.minjune.kim@gmail.com>
Thu, 27 Aug 2015 04:21:52 +0000 (13:21 +0900)
committerMarcel Holtmann <marcel@holtmann.org>
Fri, 28 Aug 2015 19:00:37 +0000 (21:00 +0200)
Signed-off-by: Minjune Kim <infinite.minjune.kim@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
drivers/bluetooth/btusb.c

index f759dea7d3baeee54da02784df91417e4632f3f0..b6aceaf82aa88c7617c4fd8e93506b8461314426 100644 (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
         * 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) {
                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;
 
-               /* 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
                 * contains proper Intel_NOP commands to align the fragments
                 * as needed.