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,
bharat@chelsio.com, benve@cisco.com, satishkh@cisco.com,
claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
wei.fang@nxp.com, xiaoning.wang@nxp.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
bryan.whitehead@microchip.com, ecree.xilinx@gmail.com,
rosenp@gmail.com, imx@lists.linux.dev
Subject: Re: [PATCH net-next v2 0/5] eth: migrate to new RXFH callbacks (get-only drivers)
Date: Tue, 17 Jun 2025 01:40:53 +0000 [thread overview]
Message-ID: <175012445324.2579607.13530180263957478401.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250614180638.4166766-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 14 Jun 2025 11:06:33 -0700 you wrote:
> Migrate the drivers which only implement ETHTOOL_GRXFH to
> the recently added dedicated .get_rxfh_fields ethtool callback.
>
> v2:
> - fix enetc
> - move the sfc falcon patch to later series in case I need to refactor
> v1: https://lore.kernel.org/20250613005409.3544529-1-kuba@kernel.org
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] eth: cisco: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/b4512e36ec9e
- [net-next,v2,2/5] eth: cxgb4: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/8d90593fd539
- [net-next,v2,3/5] eth: lan743x: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/a689e2300e17
- [net-next,v2,4/5] eth: e1000e: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/b8379a59b282
- [net-next,v2,5/5] eth: enetc: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/9a9f7ce8cb77
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-06-17 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 18:06 [PATCH net-next v2 0/5] eth: migrate to new RXFH callbacks (get-only drivers) Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 1/5] eth: cisco: migrate to new RXFH callbacks Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 2/5] eth: cxgb4: " Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 3/5] eth: lan743x: " Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 4/5] eth: e1000e: " Jakub Kicinski
2025-06-16 18:07 ` Tony Nguyen
2025-06-14 18:06 ` [PATCH net-next v2 5/5] eth: enetc: " Jakub Kicinski
2025-06-15 7:41 ` Joe Damato
2025-06-16 1:32 ` Wei Fang
2025-06-17 1:40 ` 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=175012445324.2579607.13530180263957478401.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=benve@cisco.com \
--cc=bharat@chelsio.com \
--cc=bryan.whitehead@microchip.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rosenp@gmail.com \
--cc=satishkh@cisco.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