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,
ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next 0/9] net: ethtool: add dedicated RXFH driver callbacks
Date: Fri, 13 Jun 2025 00:50:40 +0000 [thread overview]
Message-ID: <174977584001.169232.17739613101853165487.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250611145949.2674086-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Jun 2025 07:59:40 -0700 you wrote:
> Andrew asked me to plumb the RXFH header fields configuration
> thru to netlink. Before we do that we need to clean up the driver
> facing API a little bit. Right now RXFH configuration shares the
> callbacks with n-tuple filters. The future of n-tuple filters
> is uncertain within netlink. Separate the two for clarity both
> of the core code and the driver facing API.
>
> [...]
Here is the summary with links:
- [net-next,1/9] net: ethtool: copy the rxfh flow handling
https://git.kernel.org/netdev/net-next/c/f4f126535546
- [net-next,2/9] net: ethtool: remove the duplicated handling from rxfh and rxnfc
https://git.kernel.org/netdev/net-next/c/2a644c5cecc0
- [net-next,3/9] net: ethtool: require drivers to opt into the per-RSS ctx RXFH
https://git.kernel.org/netdev/net-next/c/fac4b41741b5
- [net-next,4/9] net: ethtool: add dedicated callbacks for getting and setting rxfh fields
https://git.kernel.org/netdev/net-next/c/9bb00786fc61
- [net-next,5/9] eth: remove empty RXFH handling from drivers
https://git.kernel.org/netdev/net-next/c/86b2315e7041
- [net-next,6/9] eth: fbnic: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/2a34007ba977
- [net-next,7/9] net: drv: vmxnet3: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/2f14765d6397
- [net-next,8/9] net: drv: virtio: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/63d474cfb596
- [net-next,9/9] net: drv: hyperv: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/6867fbe3a9f4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-06-13 0:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 14:59 [PATCH net-next 0/9] net: ethtool: add dedicated RXFH driver callbacks Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 1/9] net: ethtool: copy the rxfh flow handling Jakub Kicinski
2025-06-12 21:02 ` Joe Damato
2025-06-11 14:59 ` [PATCH net-next 2/9] net: ethtool: remove the duplicated handling from rxfh and rxnfc Jakub Kicinski
2025-06-12 21:34 ` Joe Damato
2025-06-11 14:59 ` [PATCH net-next 3/9] net: ethtool: require drivers to opt into the per-RSS ctx RXFH Jakub Kicinski
2025-06-12 21:09 ` Joe Damato
2025-06-11 14:59 ` [PATCH net-next 4/9] net: ethtool: add dedicated callbacks for getting and setting rxfh fields Jakub Kicinski
2025-06-13 5:36 ` Joe Damato
2025-06-13 14:39 ` Jakub Kicinski
2025-06-18 17:25 ` Dan Carpenter
2025-06-18 18:35 ` Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 5/9] eth: remove empty RXFH handling from drivers Jakub Kicinski
2025-06-12 3:21 ` Ziwei Xiao
2025-06-11 14:59 ` [PATCH net-next 6/9] eth: fbnic: migrate to new RXFH callbacks Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 7/9] net: drv: vmxnet3: " Jakub Kicinski
2025-06-11 14:59 ` [PATCH net-next 8/9] net: drv: virtio: " Jakub Kicinski
2025-06-13 0:42 ` Jason Wang
2025-06-11 14:59 ` [PATCH net-next 9/9] net: drv: hyperv: " Jakub Kicinski
2025-06-13 0:50 ` patchwork-bot+netdevbpf [this message]
2025-06-25 6:44 ` [PATCH net-next 0/9] net: ethtool: add dedicated RXFH driver callbacks Gal Pressman
2025-06-25 20:17 ` Jakub Kicinski
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=174977584001.169232.17739613101853165487.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.