From: Hans Zhang <hans.zhang@cixtech.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Peter Chen <peter.chen@cixtech.com>,
Fugang Duan <fugang.duan@cixtech.com>,
CIX Linux Kernel Upstream Group <cix-kernel-upstream@cixtech.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] mailbox: cix: Fix spelling mistake "overlow" -> "overflow"
Date: Tue, 22 Jul 2025 20:06:49 +0800 [thread overview]
Message-ID: <ed2b9167-2eb3-412e-9c1c-eba124560e3f@cixtech.com> (raw)
In-Reply-To: <20250722100214.3792075-1-colin.i.king@gmail.com>
On 2025/7/22 18:02, Colin Ian King wrote:
> [Some people who received this message don't often get email from colin.i.king@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> EXTERNAL EMAIL
>
> There is a spelling mistake in a dev_err message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/mailbox/cix-mailbox.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mailbox/cix-mailbox.c b/drivers/mailbox/cix-mailbox.c
> index 5bb1416c26a5..443620e8ae37 100644
> --- a/drivers/mailbox/cix-mailbox.c
> +++ b/drivers/mailbox/cix-mailbox.c
> @@ -346,7 +346,7 @@ static void cix_mbox_isr_fifo(struct mbox_chan *chan)
> /* FIFO overflow is generated */
> if (int_status & CIX_FIFO_OFLOW_INT) {
> status = cix_mbox_read(priv, CIX_FIFO_STAS);
> - dev_err(priv->dev, "fifo overlow: int_stats %d\n", status);
> + dev_err(priv->dev, "fifo overflow: int_stats %d\n", status);
> cix_mbox_write(priv, CIX_FIFO_OFLOW_INT, CIX_INT_CLEAR);
> }
> }
> --
> 2.50.0
>
Reviewed-by: Hans Zhang <hans.zhang@cixtech.com>
Best regards,
Hans
prev parent reply other threads:[~2025-07-22 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 10:02 [PATCH][next] mailbox: cix: Fix spelling mistake "overlow" -> "overflow" Colin Ian King
2025-07-22 12:06 ` Hans Zhang [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=ed2b9167-2eb3-412e-9c1c-eba124560e3f@cixtech.com \
--to=hans.zhang@cixtech.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=colin.i.king@gmail.com \
--cc=fugang.duan@cixtech.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@cixtech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).