From: Radu Rendec <radu@rendec.net>
To: Hemanth Selam <hemanth.selam@gmail.com>,
Thomas Gleixner <tglx@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/14] genirq: fix typos in comments
Date: Sun, 13 Sep 2026 14:11:14 -0400 [thread overview]
Message-ID: <20269ce23ee7deaffe5b45574ad2a21703288979.camel@rendec.net> (raw)
In-Reply-To: <20260907065303.18034-1-hemanth.selam@gmail.com>
On Mon, 2026-09-07 at 12:23 +0530, Hemanth Selam wrote:
> Fix typos in comments, 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>
> ---
> 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.
Thanks for the patch. For your next patch series, please send all the
patches in the series in a single git-send-email command and make sure
email threads are enabled. That way, all the patches in the series will
be grouped, both on lore.kernel.org and in people's mailboxes.
I tried to look up the thread on lore.kernel.org to see if the entire
series consisted solely of typo fixes. I couldn't. But then I
accidentally searched just for "typo" and noticed you had sent many of
these, across multiple subsystems. So I guess I have my answer.
Anyway, the patch itself looks good, so...
Reviewed-by: Radu Rendec <radu@rendec.net>
prev parent reply other threads:[~2026-09-13 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:53 Hemanth Selam
2026-09-13 18:11 ` Radu Rendec [this message]
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=20269ce23ee7deaffe5b45574ad2a21703288979.camel@rendec.net \
--to=radu@rendec.net \
--cc=hemanth.selam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®