diff mbox series

Bluetooth: btusb: Whitespace fixes for btusb_setup_csr()

Message ID e0f93f54-b466-53ec-20ba-2840ad125b73@gmail.com
State Accepted
Commit aa17e8ce1c20619af46fc2b472aa2d1c5e50c3cc
Headers show
Series Bluetooth: btusb: Whitespace fixes for btusb_setup_csr() | expand

Commit Message

Ismael Ferreras Morezuelas Jan. 18, 2022, 7:24 a.m. UTC 
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>
---

Split off from the HCI_FLT_CLEAR_ALL patch, as requested by Marcel.

 drivers/bluetooth/btusb.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff mbox series

Patch

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 75c83768c..b494b81f8 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -1948,10 +1948,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.