From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, opendmb@gmail.com,
florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: broadcom: migrate to .get_rx_ring_count() ethtool callback
Date: Sat, 29 Nov 2025 04:10:30 +0000 [thread overview]
Message-ID: <176438943073.896171.9965500132545324533.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251127-grxrings_broadcom-v1-0-b0b182864950@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 27 Nov 2025 02:17:14 -0800 you wrote:
> This series migrates Broadcom ethernet drivers to use the new
> .get_rx_ring_count() ethtool callback introduced in commit 84eaf4359c36
> ("net: ethtool: add get_rx_ring_count callback to optimize RX ring
> queries").
>
> This change simplifies the .get_rxnfc() implementation by
> extracting the ETHTOOL_GRXRINGS case handling into a dedicated callback,
> making the code cleaner and aligning these drivers with the updated
> ethtool API.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: bnxt: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/bba18f3ba7cc
- [net-next,2/2] net: bcmgenet: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/335d78c6161b
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:[~2025-11-29 4:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 10:17 [PATCH net-next 0/2] net: broadcom: migrate to .get_rx_ring_count() ethtool callback Breno Leitao
2025-11-27 10:17 ` [PATCH net-next 1/2] net: bnxt: extract GRXRINGS from .get_rxnfc Breno Leitao
2025-11-27 10:17 ` [PATCH net-next 2/2] net: bcmgenet: " Breno Leitao
2025-11-29 4: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=176438943073.896171.9965500132545324533.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--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