From: patchwork-bot+netdevbpf@kernel.org
To: Jijie Shao <shaojijie@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shenjian15@huawei.com, liuyonglong@huawei.com,
chenhao418@huawei.com, yangshuaisong@h-partners.com,
ningwei15@huawei.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: hibmcge: fix spelling mistakes in comments and identifiers
Date: Sun, 20 Sep 2026 00:10:06 +0000 [thread overview]
Message-ID: <178986300664.1499536.13577301366145990985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915132341.1138610-1-shaojijie@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Sep 2026 21:23:41 +0800 you wrote:
> Fix several typos found in the driver:
>
> - hbg_irq.c: macro parameter "ndde_reset" -> "need_reset"
> - hbg_txrx.c: macro "hbg_queue_next_prt" -> "hbg_queue_next_ptr"
> (and its call sites)
> - hbg_txrx.c: function "hbg_ring_page_pool_destory" ->
> "hbg_ring_page_pool_destroy"
> - hbg_common.h: comment "after rest" -> "after reset"
> - hbg_reg.h: register macro "HBG_REG_BRUST_LENGTH_*" ->
> "HBG_REG_BURST_LENGTH_*" (and references in hbg_hw.c)
>
> [...]
Here is the summary with links:
- [net-next] net: hibmcge: fix spelling mistakes in comments and identifiers
https://git.kernel.org/netdev/net-next/c/5ac134441dc8
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:[~2026-09-20 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 13:23 [PATCH net-next] net: hibmcge: fix spelling mistakes in comments and identifiers Jijie Shao
2026-09-20 0: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=178986300664.1499536.13577301366145990985.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=ningwei15@huawei.com \
--cc=pabeni@redhat.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.com \
--cc=yangshuaisong@h-partners.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.