From: Hemanth Selam <hemanth.selam@gmail.com>
To: Thomas Gleixner <tglx@kernel.org>
Cc: Radu Rendec <radu@rendec.net>, linux-kernel@vger.kernel.org
Subject: [PATCH v2] genirq: fix typos in comments
Date: Fri, 9 Oct 2026 12:18:07 +0530 [thread overview]
Message-ID: <20261009064807.70345-1-hemanth.selam@gmail.com> (raw)
Correct the spelling of "descriptor" and "preceded" in the kernel-doc
for msi_insert_desc() and msi_next_desc().
Reviewed-by: Radu Rendec <radu@rendec.net>
Link: https://lore.kernel.org/all/20260907065303.18034-1-hemanth.selam@gmail.com/
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
Resend of a patch that has been reviewed but not picked up.
It went out on 7 September as patch 01/14 of a batch sent as fourteen
separate mails rather than one threaded series, which Radu rightly
pointed out made it hard to see what the series contained. It is on
its own here, with his Reviewed-by collected. Both typos are still
present in tip and linux-next as of today.
kernel/irq/msi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c
index fb5f372215bf..b22d74496af1 100644
--- a/kernel/irq/msi.c
+++ b/kernel/irq/msi.c
@@ -142,7 +142,7 @@ static int msi_insert_desc(struct device *dev, struct msi_desc *desc,
* insert it at @init_desc->msi_index
*
* @dev: Pointer to the device for which the descriptor is allocated
- * @domid: The id of the interrupt domain to which the desriptor is added
+ * @domid: The id of the interrupt domain to which the descriptor is added
* @init_desc: Pointer to an MSI descriptor to initialize the new descriptor
*
* Return: 0 on success or an appropriate failure code.
@@ -416,7 +416,7 @@ EXPORT_SYMBOL_GPL(msi_domain_first_desc);
* @domid: The id of the interrupt domain which should be walked.
* @filter: Descriptor state filter
*
- * The first invocation of msi_next_desc() has to be preceeded by a
+ * The first invocation of msi_next_desc() has to be preceded by a
* successful invocation of __msi_first_desc(). Consecutive invocations are
* only valid if the previous one was successful. All these operations have
* to be done within the same MSI mutex held region.
--
2.47.3
reply other threads:[~2026-10-09 6:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261009064807.70345-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=radu@rendec.net \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®