From: Marc Zyngier <maz@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Anup Patel <Anup.Patel@wdc.com>,
tglx@linutronix.de, jason@lakedaemon.net,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, kernel-team@android.com,
Palmer Dabbelt <palmerdabbelt@google.com>
Subject: Re: [PATCH] irqchip: riscv-intc: Fix a typo in a pr_warn()
Date: Fri, 12 Jun 2020 15:06:29 +0100 [thread overview]
Message-ID: <edd04e6af3c16eabc83f28fe650a36f0@kernel.org> (raw)
In-Reply-To: <20200611175302.253540-1-palmer@dabbelt.com>
On 2020-06-11 18:53, Palmer Dabbelt wrote:
> From: Palmer Dabbelt <palmerdabbelt@google.com>
>
> Anup originally re-spun his patch set to include this fix, but it was a
> bit too
> late for my PR so I've split it out.
>
> Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
> ---
> drivers/irqchip/irq-riscv-intc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-riscv-intc.c
> b/drivers/irqchip/irq-riscv-intc.c
> index a6f97fa6ff69..8017f6d32d52 100644
> --- a/drivers/irqchip/irq-riscv-intc.c
> +++ b/drivers/irqchip/irq-riscv-intc.c
> @@ -99,7 +99,7 @@ static int __init riscv_intc_init(struct device_node
> *node,
>
> hartid = riscv_of_parent_hartid(node);
> if (hartid < 0) {
> - pr_warn("unable to fine hart id for %pOF\n", node);
> + pr_warn("unable to find hart id for %pOF\n", node);
> return 0;
> }
I'll pick it post -rc1, once I merge Linus' tree into mine.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-06-12 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 17:53 [PATCH] irqchip: riscv-intc: Fix a typo in a pr_warn() Palmer Dabbelt
2020-06-12 14:06 ` Marc Zyngier [this message]
2020-06-21 14:20 ` Marc Zyngier
2020-06-30 10:11 ` [tip: irq/urgent] irqchip/riscv-intc: " tip-bot2 for Palmer Dabbelt
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=edd04e6af3c16eabc83f28fe650a36f0@kernel.org \
--to=maz@kernel.org \
--cc=Anup.Patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=jason@lakedaemon.net \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
/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