From: patchwork-bot+netdevbpf@kernel.org
To: WangYuli <wangyuli@uniontech.com>
Cc: michael.chan@broadcom.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
pavan.chebbi@broadcom.com, mchan@broadcom.com, jdmason@kudzu.us,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mcarlson@broadcom.com,
benli@broadcom.com, sbaddipa@broadcom.com, linas@austin.ibm.com,
Ramkrishna.Vepa@neterion.com, raghavendra.koushik@neterion.com,
wenxiong@us.ibm.com, jeff@garzik.org,
vasundhara-v.volam@broadcom.com
Subject: Re: [PATCH] eth: Fix typo 'accelaration'. 'exprienced' and 'rewritting'
Date: Sun, 20 Oct 2024 16:10:42 +0000 [thread overview]
Message-ID: <172944064224.3604255.1585916865196633858.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <90D42CB167CA0842+20241018021910.31359-1-wangyuli@uniontech.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Andrew Lunn <andrew@lunn.ch>:
On Fri, 18 Oct 2024 10:19:10 +0800 you wrote:
> There are some spelling mistakes of 'accelaration', 'exprienced' and
> 'rewritting' in comments which should be 'acceleration', 'experienced'
> and 'rewriting'.
>
> Suggested-by: Simon Horman <horms@kernel.org>
> Link: https://lore.kernel.org/all/20241017162846.GA51712@kernel.org/
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
>
> [...]
Here is the summary with links:
- eth: Fix typo 'accelaration'. 'exprienced' and 'rewritting'
https://git.kernel.org/netdev/net-next/c/9e2ffec543b0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-20 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 2:19 [PATCH] eth: Fix typo 'accelaration'. 'exprienced' and 'rewritting' WangYuli
2024-10-18 10:09 ` Donald Hunter
2024-10-18 19:29 ` Simon Horman
2024-10-20 16:10 ` patchwork-bot+netdevbpf [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=172944064224.3604255.1585916865196633858.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Ramkrishna.Vepa@neterion.com \
--cc=benli@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdmason@kudzu.us \
--cc=jeff@garzik.org \
--cc=kuba@kernel.org \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=raghavendra.koushik@neterion.com \
--cc=sbaddipa@broadcom.com \
--cc=vasundhara-v.volam@broadcom.com \
--cc=wangyuli@uniontech.com \
--cc=wenxiong@us.ibm.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).