[PATCH v2 19/22] usb: serial: fix a few spelling mistakes in comments
From: Shunbo Shi
Date: Tue Nov 10 2026 - 03:27:21 EST
No functional changes.
Signed-off-by: Shunbo Shi <shishunbo@xxxxxxxxxxxxxxxxxxxx>
---
drivers/usb/serial/cypress_m8.c | 2 +-
drivers/usb/serial/f81534.c | 8 ++++----
drivers/usb/serial/mos7720.c | 2 +-
drivers/usb/serial/oti6858.c | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/serial/cypress_m8.c b/drivers/usb/serial/cypress_m8.c
index 78fb1389b34c..bd9b68b691de 100644
--- a/drivers/usb/serial/cypress_m8.c
+++ b/drivers/usb/serial/cypress_m8.c
@@ -462,7 +462,7 @@ static int cypress_generic_port_probe(struct usb_serial_port *port)
return -ENOMEM;
}
- /* Skip reset for FRWD device. It is a workaound:
+ /* Skip reset for FRWD device. It is a workaround:
device hangs if it receives SET_CONFIGURE in Configured
state. */
if (!is_frwd(serial->dev))
diff --git a/drivers/usb/serial/f81534.c b/drivers/usb/serial/f81534.c
index 0037767e4bbf..502c1c0260ec 100644
--- a/drivers/usb/serial/f81534.c
+++ b/drivers/usb/serial/f81534.c
@@ -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)
@@ -824,9 +824,9 @@ static bool f81534_check_port_hw_disabled(struct usb_serial *serial, int phy)
* f81534_calc_num_ports() will run to final we marked as "oldest version"
* for this IC.
*
- * 2rd is designed to more generic to use any transceiver and this is our
+ * 2nd is designed to more generic to use any transceiver and this is our
* mass production type. We'll save data in F81534_CUSTOM_ADDRESS_START
- * (0x2f00) with 9bytes. The 1st byte is a indicater. If the token is
+ * (0x2f00) with 9bytes. The 1st byte is a indicator. If the token is
* F81534_CUSTOM_VALID_TOKEN(0xf0), the IC is 2nd gen type, the following
* 4bytes save port mode (0:RS232/1:RS485 Invert/2:RS485), and the last
* 4bytes save GPIO state(value from 0~7 to represent 3 GPIO output pin).
diff --git a/drivers/usb/serial/mos7720.c b/drivers/usb/serial/mos7720.c
index 104f43a8f4d8..312fa11cea95 100644
--- a/drivers/usb/serial/mos7720.c
+++ b/drivers/usb/serial/mos7720.c
@@ -1208,7 +1208,7 @@ static int set_higher_rates(struct moschip_port *mos7720_port,
/***********************************************
* Set for higher rates *
***********************************************/
- /* writing baud rate verbatum into uart clock field clearly not right */
+ /* writing baud rate verbatim into uart clock field clearly not right */
if (port_number == 0)
sp_reg = MOS7720_SP1_REG;
else
diff --git a/drivers/usb/serial/oti6858.c b/drivers/usb/serial/oti6858.c
index c6364e8ff71f..0e527fe56da0 100644
--- a/drivers/usb/serial/oti6858.c
+++ b/drivers/usb/serial/oti6858.c
@@ -13,7 +13,7 @@
* Warning! You use this driver on your own risk! The only official
* description of this device I have is datasheet from manufacturer,
* and it doesn't contain almost any information needed to write a driver.
- * Almost all knowlegde used while writing this driver was gathered by:
+ * Almost all knowledge used while writing this driver was gathered by:
* - analyzing traffic between device and the M$ Windows 2000 driver,
* - trying different bit combinations and checking pin states
* with a voltmeter,
--
2.53.0