From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Colin Ian King <coking@nvidia.com>
Cc: "Chin-Ting Kuo" <chin-ting_kuo@aspeedtech.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Mark Brown" <broonie@kernel.org>,
"Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"
Date: Fri, 17 Oct 2025 08:26:56 +0200 [thread overview]
Message-ID: <8fa346e3-308f-4ecb-af57-0fd643351765@molgen.mpg.de> (raw)
In-Reply-To: <20251016153000.9142-1-coking@nvidia.com>
Dear Colin,
Thank you for the patch.
Am 16.10.25 um 17:30 schrieb Colin Ian King:
> There is a spelling mistake in a dev_warn message. Fix it.
>
> Signed-off-by: Colin Ian King <coking@nvidia.com>
> ---
> drivers/spi/spi-aspeed-smc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/spi/spi-aspeed-smc.c b/drivers/spi/spi-aspeed-smc.c
> index 0c3de371fd39..f3a7189afd51 100644
> --- a/drivers/spi/spi-aspeed-smc.c
> +++ b/drivers/spi/spi-aspeed-smc.c
> @@ -539,7 +539,7 @@ static int aspeed_spi_trim_window_size(struct aspeed_spi *aspi)
> } while (total_sz > aspi->ahb_window_size);
>
> if (trimmed) {
> - dev_warn(aspi->dev, "Window size after triming:\n");
> + dev_warn(aspi->dev, "Window size after trimming:\n");
> for (cs = 0; cs < aspi->data->max_cs; cs++) {
> dev_warn(aspi->dev, "CE%d: 0x%08x\n",
> cs, chips[cs].ahb_window_size);
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
next prev parent reply other threads:[~2025-10-17 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 15:30 [PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming" Colin Ian King
2025-10-17 1:05 ` Chin-Ting Kuo
2025-10-17 6:26 ` Paul Menzel [this message]
2025-10-17 11:25 ` Mark Brown
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=8fa346e3-308f-4ecb-af57-0fd643351765@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=andrew@codeconstruct.com.au \
--cc=broonie@kernel.org \
--cc=chin-ting_kuo@aspeedtech.com \
--cc=clg@kaod.org \
--cc=coking@nvidia.com \
--cc=joel@jms.id.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).