Bluetooth: btusb: Whitespace fixes for btusb_setup_csr()

Properly align the list items of the quirk for readability.
No functional changes intended. Trivial stuff.

Fixes: 0671c0662383e ("Bluetooth: btusb: Add workaround for remote-wakeup issues with Barrot 8041a02 fake CSR controllers")
Signed-off-by: Ismael Ferreras Morezuelas <swyterzone@gmail.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 06effcae0e3fdc1fe4af54997a1b2a49eb226195..aefa0ee293f362cad1b6cfe7a2587835600b1fe9 100644 (file)
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -2062,10 +2062,10 @@ static int btusb_setup_csr(struct hci_dev *hdev)
                 * These controllers are really messed-up.
                 *
                 * 1. Their bulk RX endpoint will never report any data unless
-                * the device was suspended at least once (yes, really).
+                *    the device was suspended at least once (yes, really).
                 * 2. They will not wakeup when autosuspended and receiving data
-                * on their bulk RX endpoint from e.g. a keyboard or mouse
-                * (IOW remote-wakeup support is broken for the bulk endpoint).
+                *    on their bulk RX endpoint from e.g. a keyboard or mouse
+                *    (IOW remote-wakeup support is broken for the bulk endpoint).
                 *
                 * To fix 1. enable runtime-suspend, force-suspend the
                 * HCI and then wake-it up by disabling runtime-suspend.