From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: claudiu.manoil@nxp.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ioana.ciornei@nxp.com,
vladimir.oltean@nxp.com, wei.fang@nxp.com, xiaoning.wang@nxp.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH net-next 0/3] net: freescale: migrate to .get_rx_ring_count() ethtool callback
Date: Mon, 01 Dec 2025 20:00:11 +0000 [thread overview]
Message-ID: <176461921179.2515760.13851100903689517014.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128-gxring_freescale-v1-0-22a978abf29e@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Nov 2025 05:11:44 -0800 you wrote:
> This series migrates Freescale 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,1/3] net: gianfar: convert to use .get_rx_ring_count
https://git.kernel.org/netdev/net-next/c/d3fbfb8b2c4a
- [net-next,2/3] net: dpaa2: convert to use .get_rx_ring_count
https://git.kernel.org/netdev/net-next/c/b2d633926901
- [net-next,3/3] net: enetc: convert to use .get_rx_ring_count
https://git.kernel.org/netdev/net-next/c/ca8df5b877d4
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-12-01 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 13:11 [PATCH net-next 0/3] net: freescale: migrate to .get_rx_ring_count() ethtool callback Breno Leitao
2025-11-28 13:11 ` [PATCH net-next 1/3] net: gianfar: convert to use .get_rx_ring_count Breno Leitao
2025-11-30 15:21 ` Simon Horman
2025-11-28 13:11 ` [PATCH net-next 2/3] net: dpaa2: " Breno Leitao
2025-11-30 15:21 ` Simon Horman
2025-11-28 13:11 ` [PATCH net-next 3/3] net: enetc: " Breno Leitao
2025-11-30 15:22 ` Simon Horman
2025-12-01 20:00 ` 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=176461921179.2515760.13851100903689517014.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=ioana.ciornei@nxp.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=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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).