From: Radu Rendec <radu@rendec.net>
To: Hemanth Selam <hemanth.selam@gmail.com>,
Talel Shenhar <talel@amazon.com>,
Thomas Gleixner <tglx@kernel.org>,
Marc Zyngier <maz@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 10/14] irqchip: fix repeated words in comments
Date: Sun, 13 Sep 2026 14:35:02 -0400 [thread overview]
Message-ID: <67e1861034a1083843c876deae4af9733f4a09ae.camel@rendec.net> (raw)
In-Reply-To: <20260907065659.12034-1-hemanth.selam@gmail.com>
On Mon, 2026-09-07 at 12:26 +0530, Hemanth Selam wrote:
> Drop words accidentally written twice, reported by checkpatch.pl as a
> possible repeated word. Only touches comments, no code changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
> drivers/irqchip/irq-al-fic.c | 2 +-
> drivers/irqchip/irq-gic-v3.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Same comment as before, for patch 02/14. I think this should be split
into two patches in the same series.
Applying many patches is easy/cheap. Dealing with merge conflicts
across different drivers when backporting patches, not so much.
>
> diff --git a/drivers/irqchip/irq-al-fic.c b/drivers/irqchip/irq-al-fic.c
> index d10ac9b63c99..760317db9dba 100644
> --- a/drivers/irqchip/irq-al-fic.c
> +++ b/drivers/irqchip/irq-al-fic.c
> @@ -180,7 +180,7 @@ static int al_fic_register(struct device_node *node,
> * @name: name of the fic
> * @parent_irq: interrupt of parent
> *
> - * This API will configure the fic hardware to to work in wire mode.
> + * This API will configure the fic hardware to work in wire mode.
> * In wire mode, fic hardware is generating a wire ("wired") interrupt.
> * Interrupt can be generated based on positive edge or level - configuration is
> * to be determined based on connected hardware to this fic.
> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> index 6e1fa5b247fc..69ca208eeee6 100644
> --- a/drivers/irqchip/irq-gic-v3.c
> +++ b/drivers/irqchip/irq-gic-v3.c
> @@ -687,7 +687,7 @@ static void gic_eoimode1_eoi_irq(struct irq_data *d)
> {
> /*
> * No need to deactivate an LPI, or an interrupt that
> - * is is getting forwarded to a vcpu.
> + * is getting forwarded to a vcpu.
> */
> if (irqd_to_hwirq(d) >= 8192 || irqd_is_forwarded_to_vcpu(d))
> return;
prev parent reply other threads:[~2026-09-13 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:56 [PATCH 10/14] irqchip: fix repeated words in comments Hemanth Selam
2026-09-13 18:35 ` 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=67e1861034a1083843c876deae4af9733f4a09ae.camel@rendec.net \
--to=radu@rendec.net \
--cc=hemanth.selam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=talel@amazon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.