From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com
Subject: Re: [PATCH net-next] eth: bnxt: rename ring_err_stats -> ring_drv_stats
Date: Wed, 25 Feb 2026 04:09:53 +0000 [thread overview]
Message-ID: <177199259379.36698.16362733482941267976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260223203702.4137801-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 23 Feb 2026 12:37:01 -0800 you wrote:
> We recently added GRO stats to bnxt, which are maintained
> by the driver. Having "err" in the name of the struct for
> ring stats no longer makes sense (as pointed out by Michael,
> see Link).
>
> Rename them to "drv" stats, as these are all maintained
> by the driver (even if partially based on info from descriptors).
> Michael suggested calling these misc, happy to go back to
> that. IMHO "drv" is a bit more meaningful that "misc".
>
> [...]
Here is the summary with links:
- [net-next] eth: bnxt: rename ring_err_stats -> ring_drv_stats
https://git.kernel.org/netdev/net-next/c/6c32b0765067
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-02-25 4:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 20:37 [PATCH net-next] eth: bnxt: rename ring_err_stats -> ring_drv_stats Jakub Kicinski
2026-02-23 21:21 ` Michael Chan
2026-02-25 4:09 ` 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=177199259379.36698.16362733482941267976.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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