usb: fix typos and repeated words in comments
Subsystems (2)
cover usb: fix typos and repeated words in comments
This corrects 2 misspellings and repeated words in comments. Each is a separate patch so that any one of them can be dropped without touching the rest.
Nothing outside comments changes. Every touched C file was checked by dropping its comments, replacing each string literal with a placeholder and collapsing whitespace; what remained was identical before and after, so the compiled code cannot differ.
The mistakes were found with scripts/checkpatch.pl against the list in scripts/spelling.txt. The scanning, the edits and the changelogs were produced with Cursor running the claude-opus-5 model, from a request to find and fix spelling mistakes across the tree, and every correction was then re-checked by the comparison described above. Words that name an identifier were left alone deliberately, even when they read as typos, because correcting the prose would make the comment disagree with the code it describes.
Tested by building x86_64 defconfig at v7.3-rc1-269-gbc35965f6940, which is clean. Nothing else was built, so any patch touching code that x86_64 defconfig does not compile has been read but not compiled.
Hemanth Selam (2):
usb: serial: fix typos in comments
usb: serial: fix repeated words in comments
drivers/usb/serial/f81534.c | 4 ++-- drivers/usb/serial/ftdi_sio_ids.h | 2 +- drivers/usb/serial/keyspan_usa28msg.h | 2 +- drivers/usb/serial/mct_u232.h | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-)
Signature · 1 line
2.48.1
PATCH 1/2 usb: serial: fix typos in comments
Fix typos in comments, reported by scripts/checkpatch.pl using the misspelling list in scripts/spelling.txt. Only touches comments, no code changes.
--- drivers/usb/serial/f81534.c | 4 ++-- drivers/usb/serial/ftdi_sio_ids.h | 2 +- drivers/usb/serial/keyspan_usa28msg.h | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
drivers/usb/serial/f81534.c +2 -2
@@ -83,7 +83,7 @@#define F81534_TOKEN_MSR_CHANGE 0x04/* -* We used interal SPI bus to access FLASH section. We must wait the SPI bus to +* We used internal SPI bus to access FLASH section. We must wait the SPI bus to * idle if we performed any command. * * SPI Bus status register: F81534_BUS_REG_STATUS
@@ -755,7 +755,7 @@ static int f81534_find_config_idx(struct usb_serial *serial, u8 *index)* The F81532/534 will not report serial port to USB serial subsystem when * H/W DCD/DSR/CTS/RI/RX pin connected to ground. * -* To detect RX pin status, we'll enable MCR interal loopback, disable it and +* To detect RX pin status, we'll enable MCR internal loopback, disable it and * delayed for 60ms. It connected to ground If LSR register report UART_LSR_BI. */ static bool f81534_check_port_hw_disabled (struct usb_serial *serial,int phy)
drivers/usb/serial/ftdi_sio_ids.h +1 -1
@@ -770,7 +770,7 @@* Definitions for Icom Inc. devices */ #define ICOM_VID 0x0C26/* Icom vendor ID */ -/* Note: ID-1 is a communications tranceiver for HAM-radio operators */ +/* Note: ID-1 is a communications transceiver for HAM-radio operators */ #define ICOM_ID_1_PID 0x0004/* ID-1 USB to RS-232 */ /* Note: OPC is an Optional cable to connect an Icom Tranceiver */ #define ICOM_OPC_U_UC_PID 0x0018/* OPC-478UC, OPC-1122U cloning cable */
drivers/usb/serial/keyspan_usa28msg.h +1 -1
@@ -61,7 +61,7 @@ with a total data length of 63. USB IN (USA28 -> host, receive) messages contain data and parity - if parity is configred, thusly: + if parity is configured, thusly: DAT PAR DAT PAR DAT PAR ...
Signature · 1 line
2.48.1
PATCH 2/2 usb: serial: fix repeated words in comments
In reply to Hemanth SelamDrop words accidentally written twice, reported by checkpatch.pl as a possible repeated word. Only touches comments, no code changes.
--- drivers/usb/serial/mct_u232.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/usb/serial/mct_u232.h +2 -2
@@ -273,13 +273,13 @@ static int mct_u232_calculate_baud_rate(struct usb_serial *serial,* Bit 5: Data Set Ready (DSR). Reflects the state of the DSR line on the UART. * Bit 4: Clear To Send (CTS). Reflects the state of the CTS line on the UART. * Bit 3: Delta Data Carrier Detect (DDCD). Set to "1" if the -DCD line has -* changed state one more more times since the last time the MSR was +* changed state one more times since the last time the MSR was * read by the host. * Bit 2: Trailing Edge Ring Indicator (TERI). Set to "1" if the -RI line has * had a low to high transition since the last time the MSR was read by * the host. * Bit 1: Delta Data Set Ready (DDSR). Set to "1" if the -DSR line has changed -* state one more more times since the last time the MSR was read by the +* state one more times since the last time the MSR was read by the * host. * Bit 0: Delta Clear To Send (DCTS). Set to "1" if the -CTS line has changed * state one more times since the last time the MSR was read by the
Signature · 1 line
2.48.1