From: Marc Zyngier <maz@kernel.org>
To: Jason Wang <wangborong@cdjrlc.com>
Cc: tsbogend@alpha.franken.de, fancer.lancer@gmail.com,
tglx@linutronix.de, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/mips-gic: Fix comment typo
Date: Tue, 19 Jul 2022 13:53:58 +0100 [thread overview]
Message-ID: <87cze1z2jd.wl-maz@kernel.org> (raw)
In-Reply-To: <20220716041619.33629-1-wangborong@cdjrlc.com>
On Sat, 16 Jul 2022 05:16:19 +0100,
Jason Wang <wangborong@cdjrlc.com> wrote:
>
> The double `the' is duplicated in the comment, remove one.
>
> Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
> ---
> drivers/irqchip/irq-mips-gic.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-mips-gic.c b/drivers/irqchip/irq-mips-gic.c
> index 8a9efb6ae587..9464af4b53e7 100644
> --- a/drivers/irqchip/irq-mips-gic.c
> +++ b/drivers/irqchip/irq-mips-gic.c
> @@ -494,7 +494,7 @@ static int gic_irq_domain_map(struct irq_domain *d, unsigned int virq,
> map = GIC_MAP_PIN_MAP_TO_PIN | gic_cpu_pin;
>
> /*
> - * If adding support for more per-cpu interrupts, keep the the
> + * If adding support for more per-cpu interrupts, keep the
> * array in gic_all_vpes_irq_cpu_online() in sync.
> */
> switch (intr) {
Please send those as a series, not as one patch every other day.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-07-19 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 4:16 [PATCH] irqchip/mips-gic: Fix comment typo Jason Wang
2022-07-19 12:53 ` Marc Zyngier [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 20:01 Jason Wang
2022-08-27 13:20 ` Serge Semin
2022-09-07 14:55 ` Serge Semin
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=87cze1z2jd.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=wangborong@cdjrlc.com \
/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.