[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aO4Y9sC1pwgq2kNc@horms.kernel.org>
Date: Tue, 14 Oct 2025 10:33:42 +0100
From: Simon Horman <horms@...nel.org>
To: Alok Tiwari <alok.a.tiwari@...cle.com>
Cc: alexanderduyck@...com, kuba@...nel.org, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
kernel-team@...a.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] eth: fbnic: fix various typos in comments and
strings
On Mon, Oct 13, 2025 at 09:05:02AM -0700, Alok Tiwari wrote:
> Fix several minor typos and grammatical errors in comments and log
> (in fbnic firmware, PCI, and time modules)
>
> Changes include:
> - "cordeump" -> "coredump"
> - "of" -> "off" in RPC config comment
> - "healty" -> "healthy" in firmware heartbeat comment
> - "Firmware crashed detected!" -> "Firmware crash detected!"
> - "The could be caused" -> "This could be caused"
> - "lockng" -> "locking" in fbnic_time.c
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@...cle.com>
Thanks, this makes sense to me.
Curiously invoking codespell locally only picked up the healthy typo.
In any case, these file are codespell-clean, in my environment, with
this patch applied.
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists