[PATCH] nvme: fix typo "occuring" in comment

[PATCH] nvme: fix typo "occuring" in comment

[Hemanth Selam]

Correct "occuring" to "occurring", reported by scripts/checkpatch.pl using
the misspelling list in scripts/spelling.txt.  Only touches comments, no
code changes.

Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
 drivers/nvme/host/multipath.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/nvme/host/multipath.c b/drivers/nvme/host/multipath.c
index 75dbb58286a3..4d931cb1162f 100644
--- a/drivers/nvme/host/multipath.c
+++ b/drivers/nvme/host/multipath.c
@@ -773,7 +773,7 @@ int nvme_mpath_alloc_disk(struct nvme_ctrl *ctrl, struct nvme_ns_head *head)
 	head->disk->private_data = head;
 
 	/*
-	 * We need to suppress the partition scan from occuring within the
+	 * We need to suppress the partition scan from occurring within the
 	 * controller's scan_work context. If a path error occurs here, the IO
 	 * will wait until a path becomes available or all paths are torn down,
 	 * but that action also occurs within scan_work, so it would deadlock.
-- 
2.48.1

Re: [PATCH] nvme: fix typo "occuring" in comment

[Keith Busch]

On Fri, Sep 04, 2026 at 04:57:21PM +0530, Hemanth Selam wrote:
> Correct "occuring" to "occurring", reported by scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt.  Only touches comments, no
> code changes.

Generally, but not always, we don't take pure comment typo fixes because
it creates a conflict point for potentially stable fixes in the
surrounding code.