[PATCH v2] misc: fix typos in comments
From: Hemanth Selam
Date: Tue Oct 06 2026 - 02:01:47 EST
Fix typos in comments, reported by scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt. One further misspelling of
"respectively" in genwqe/card_base.c is fixed as well: it is not in
scripts/spelling.txt, but it sits a few lines from one that checkpatch
does report. Only comments are touched, there are no code changes.
Assisted-by: LLM
Signed-off-by: Hemanth Selam <hemanth.selam@xxxxxxxxx>
---
Notes (v2):
v2:
- Drop the drivers/char/lp.c hunk. It is not under drivers/misc, which
is what the "misc:" prefix claimed. It is now sent separately, as
"char: lp: fix typo in comment".
- Also fix a second misspelling in genwqe/card_base.c, a few lines from
one already being corrected. checkpatch does not report it because
it is not listed in scripts/spelling.txt.
v1: https://lore.kernel.org/all/20260904113843.21367-1-hemanth.selam@xxxxxxxxx/
drivers/misc/gehc-achc.c | 2 +-
drivers/misc/genwqe/card_base.c | 8 ++++----
drivers/misc/genwqe/card_ddcb.c | 4 ++--
drivers/misc/genwqe/card_utils.c | 2 +-
drivers/misc/vmw_vmci/vmci_datagram.c | 2 +-
drivers/misc/vmw_vmci/vmci_queue_pair.c | 2 +-
6 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/misc/gehc-achc.c b/drivers/misc/gehc-achc.c
index 9792189c0923..2c1222edb5dc 100644
--- a/drivers/misc/gehc-achc.c
+++ b/drivers/misc/gehc-achc.c
@@ -369,7 +369,7 @@ static int ezport_firmware_flash_data(struct spi_device *spi,
dev_dbg(&spi->dev, "EzPort verify flashed data...\n");
ret = ezport_firmware_compare_data(spi, data, size);
- /* allow missing FW verfication in secure mode */
+ /* allow missing FW verification in secure mode */
if (ret == -EACCES)
ret = 0;
diff --git a/drivers/misc/genwqe/card_base.c b/drivers/misc/genwqe/card_base.c
index e602eb3c51fa..3eb843af31a5 100644
--- a/drivers/misc/genwqe/card_base.c
+++ b/drivers/misc/genwqe/card_base.c
@@ -286,7 +286,7 @@ int genwqe_flash_readback_fails(struct genwqe_dev *cd)
* @cd: GenWQE device information
*
* Note: From a design perspective it turned out to be a bad idea to
- * use codes here to specifiy the frequency/speed values. An old
+ * use codes here to specify the frequency/speed values. An old
* driver cannot understand new codes and is therefore always a
* problem. Better is to measure out the value or put the
* speed/frequency directly into a register which is always a valid
@@ -904,7 +904,7 @@ static int genwqe_reload_bistream(struct genwqe_dev *cd)
*
* Condition for the health-thread to trigger:
* a) when a kthread_stop() request comes in or
- * b) a critical GFIR occured
+ * b) a critical GFIR occurred
*
* Informational GFIRs are checked and potentially printed in
* GENWQE_HEALTH_CHECK_INTERVAL seconds.
@@ -1210,10 +1210,10 @@ static int genwqe_probe(struct pci_dev *pci_dev,
}
/**
- * genwqe_remove() - Called when device is removed (hot-plugable)
+ * genwqe_remove() - Called when device is removed (hot-pluggable)
* @pci_dev: PCI device information struct
*
- * Or when driver is unloaded respecitively when unbind is done.
+ * Or when driver is unloaded respectively when unbind is done.
*/
static void genwqe_remove(struct pci_dev *pci_dev)
{
diff --git a/drivers/misc/genwqe/card_ddcb.c b/drivers/misc/genwqe/card_ddcb.c
index 969178573940..07e2c1be22d9 100644
--- a/drivers/misc/genwqe/card_ddcb.c
+++ b/drivers/misc/genwqe/card_ddcb.c
@@ -460,7 +460,7 @@ static int genwqe_check_ddcb_queue(struct genwqe_dev *cd,
/**
* __genwqe_wait_ddcb(): Waits until DDCB is completed
* @cd: pointer to genwqe device descriptor
- * @req: pointer to requsted DDCB parameters
+ * @req: pointer to requested DDCB parameters
*
* The Service Layer will update the RETC in DDCB when processing is
* pending or done.
@@ -543,7 +543,7 @@ int __genwqe_wait_ddcb(struct genwqe_dev *cd, struct ddcb_requ *req)
return -EINVAL;
}
- /* Severe error occured. Driver is forced to stop operation */
+ /* Severe error occurred. Driver is forced to stop operation */
if (cd->card_state != GENWQE_CARD_USED) {
dev_err(&pci_dev->dev,
"[%s] err: DDCB#%d forced to stop (rc=%d)\n",
diff --git a/drivers/misc/genwqe/card_utils.c b/drivers/misc/genwqe/card_utils.c
index e3b5fb337182..7c57cb881d7f 100644
--- a/drivers/misc/genwqe/card_utils.c
+++ b/drivers/misc/genwqe/card_utils.c
@@ -1003,7 +1003,7 @@ u64 genwqe_read_vreg(struct genwqe_dev *cd, u32 reg, int func)
* @cd: genwqe device descriptor
*
* Note: From a design perspective it turned out to be a bad idea to
- * use codes here to specifiy the frequency/speed values. An old
+ * use codes here to specify the frequency/speed values. An old
* driver cannot understand new codes and is therefore always a
* problem. Better is to measure out the value or put the
* speed/frequency directly into a register which is always a valid
diff --git a/drivers/misc/vmw_vmci/vmci_datagram.c b/drivers/misc/vmw_vmci/vmci_datagram.c
index 6193a22c3ab5..73b43b097f92 100644
--- a/drivers/misc/vmw_vmci/vmci_datagram.c
+++ b/drivers/misc/vmw_vmci/vmci_datagram.c
@@ -434,7 +434,7 @@ EXPORT_SYMBOL_GPL(vmci_datagram_create_handle_priv);
* @out_handle: vmci_handle that is populated as a result of this function.
*
* Creates a host context datagram endpoint and returns a handle to
- * it. Same as vmci_datagram_create_handle_priv without the priviledge
+ * it. Same as vmci_datagram_create_handle_priv without the privilege
* flags argument.
*/
int vmci_datagram_create_handle(u32 resource_id,
diff --git a/drivers/misc/vmw_vmci/vmci_queue_pair.c b/drivers/misc/vmw_vmci/vmci_queue_pair.c
index 46bba9bef553..e1a11820be01 100644
--- a/drivers/misc/vmw_vmci/vmci_queue_pair.c
+++ b/drivers/misc/vmw_vmci/vmci_queue_pair.c
@@ -2668,7 +2668,7 @@ static ssize_t qp_dequeue_locked(struct vmci_queue *produce_q,
* @consume_qsize: Desired size of the consumer queue.
* @peer: ContextID of the peer.
* @flags: VMCI flags.
- * @priv_flags: VMCI priviledge flags.
+ * @priv_flags: VMCI privilege flags.
*
* This is the client interface for allocating the memory for a
* vmci_qp structure and then attaching to the underlying
--
2.47.3