[PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"

[PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"

[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);
-- 
2.51.0

RE: [PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"

[Chin-Ting Kuo]

Hi Colin,

Thanks for typo fix.

> -----Original Message-----
> From: Colin Ian King <coking@nvidia.com>
> Sent: Thursday, October 16, 2025 11:30 PM
> Subject: [PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"
> 
> 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(-)
> 

Reviewed-by: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>

> 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);
> --
> 2.51.0

Re: [PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"

[Paul Menzel]

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

Re: [PATCH][next] spi: aspeed: fix spelling mistake "triming" -> "trimming"

[Mark Brown]

On Thu, 16 Oct 2025 16:30:00 +0100, Colin Ian King wrote:
> There is a spelling mistake in a dev_warn message. Fix it.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: aspeed: fix spelling mistake "triming" -> "trimming"
      commit: d77daa49085b067137d0adbe3263f75a7ee13a1b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark