From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: aleksander.lobakin@intel.com, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, aleksandr.loktionov@intel.com
Subject: Re: [PATCH net-next v2 0/8] net: intel: migrate to .get_rx_ring_count() ethtool callback
Date: Thu, 27 Nov 2025 01:20:25 +0000 [thread overview]
Message-ID: <176420642599.1910295.10418248024267534204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251125-gxring_intel-v2-0-f55cd022d28b@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Nov 2025 02:19:43 -0800 you wrote:
> This series migrates Intel network 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").
>
> The new callback simplifies the .get_rxnfc() implementation by removing
> ETHTOOL_GRXRINGS handling and moving it to a dedicated callback. This provides
> a cleaner separation of concerns and aligns these drivers with the modern
> ethtool API.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] i40e: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/a8acbcbaf6d0
- [net-next,v2,2/8] iavf: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/fe0a3d7d1dca
- [net-next,v2,3/8] ice: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/8e8c00e1d213
- [net-next,v2,4/8] idpf: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/873a1942fbc6
- [net-next,v2,5/8] igb: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/d6c744f46816
- [net-next,v2,6/8] igc: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/768ce58dddb2
- [net-next,v2,7/8] ixgbevf: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/3399fd519dd4
- [net-next,v2,8/8] fm10k: extract GRXRINGS from .get_rxnfc
https://git.kernel.org/netdev/net-next/c/73d834cd1774
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-27 1:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:19 [PATCH net-next v2 0/8] net: intel: migrate to .get_rx_ring_count() ethtool callback Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 1/8] i40e: extract GRXRINGS from .get_rxnfc Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 2/8] iavf: " Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 3/8] ice: " Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 4/8] idpf: " Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 5/8] igb: " Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 6/8] igc: " Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 7/8] ixgbevf: " Breno Leitao
2025-11-25 10:19 ` [PATCH net-next v2 8/8] fm10k: " Breno Leitao
2025-11-27 1:20 ` 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=176420642599.1910295.10418248024267534204.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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