From: Simon Horman <horms@kernel.org>
To: Chu Guangqing <chuguangqing@inspur.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: sungem_phy: Fix a typo error in sungem_phy
Date: Tue, 4 Nov 2025 14:40:36 +0000 [thread overview]
Message-ID: <aQoQZFUXupfJI1nA@horms.kernel.org> (raw)
In-Reply-To: <20251103054443.2878-1-chuguangqing@inspur.com>
On Mon, Nov 03, 2025 at 01:44:43PM +0800, Chu Guangqing wrote:
> Fix a spelling mistakes for regularly
>
> Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>
> ---
> drivers/net/sungem_phy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks,
I see that with this change this file is now codespell-clean.
Reviewed-by: Simon Horman <horms@kernel.org>
...
next prev parent reply other threads:[~2025-11-04 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 5:44 [PATCH] net: sungem_phy: Fix a typo error in sungem_phy Chu Guangqing
2025-11-04 14:40 ` Simon Horman [this message]
2025-11-05 1:10 ` patchwork-bot+netdevbpf
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=aQoQZFUXupfJI1nA@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chuguangqing@inspur.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).