[PATCH] HID: logitech-hidpp: fix typos in comments

[PATCH] HID: logitech-hidpp: fix typos in comments

[Zain Aboobacker]

Fix various spelling mistakes in comments found by codespell.

Assisted-by: Claude:claude-opus-5-5 codespell
Signed-off-by: Zain Aboobacker <zainaboobacker33@gmail.com>
---
 drivers/hid/hid-logitech-hidpp.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index 9646380febac..f4bf4a39fcd9 100644
--- a/drivers/hid/hid-logitech-hidpp.c
+++ b/drivers/hid/hid-logitech-hidpp.c
@@ -108,9 +108,9 @@ MODULE_PARM_DESC(disable_tap_to_click,
  *
  * Most older devices (including the Unifying usb receiver) use the RAP protocol
  * where as most newer devices use the FAP protocol. Both protocols are
- * compatible with the underlying transport, which could be usb, Unifiying, or
+ * compatible with the underlying transport, which could be usb, Unifying, or
  * bluetooth. The message lengths are defined by the hid vendor specific report
- * descriptor for the HIDPP_SHORT report type (total message lenth 7 bytes) and
+ * descriptor for the HIDPP_SHORT report type (total message length 7 bytes) and
  * the HIDPP_LONG report type (total message length 20 bytes)
  *
  * The RAP protocol uses both report types, whereas the FAP only uses HIDPP_LONG
@@ -120,7 +120,7 @@ MODULE_PARM_DESC(disable_tap_to_click,
  * Unifying device.
  *
  * The paired device can be RAP or FAP, it will receive the message untouched
- * from the Unifiying receiver.
+ * from the Unifying receiver.
  */
 
 struct fap {
@@ -1656,7 +1656,7 @@ static int hidpp20_unifiedbattery_map_status(struct hidpp_device *hidpp,
 static int hidpp20_unifiedbattery_map_level(struct hidpp_device *hidpp,
 					    u8 battery_level)
 {
-	/* cler unsupported level bits */
+	/* clear unsupported level bits */
 	battery_level &= hidpp->battery.supported_levels_1004;
 
 	if (battery_level & FLAG_UNIFIED_BATTERY_LEVEL_FULL)
@@ -3353,7 +3353,7 @@ static int m560_input_mapping(struct hid_device *hdev, struct hid_input *hi,
 /*
  * The Logitech K400 keyboard has an embedded touchpad which is seen
  * as a mouse from the OS point of view. There is a hardware shortcut to disable
- * tap-to-click but the setting is not remembered accross reset, annoying some
+ * tap-to-click but the setting is not remembered across reset, annoying some
  * users.
  *
  * We can toggle this feature from the host by using the feature 0x6010:
-- 
2.53.0