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,
intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, jacob.e.keller@intel.com,
michal.swiatkowski@linux.intel.com, joe@dama.to
Subject: Re: [PATCH net-next v2 0/7] eth: intel: migrate to new RXFH callbacks
Date: Tue, 17 Jun 2025 01:40:52 +0000 [thread overview]
Message-ID: <175012445200.2579607.10501400435352945895.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250614180907.4167714-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:09:00 -0700 you wrote:
> Migrate Intel drivers to the recently added dedicated .get_rxfh_fields
> and .set_rxfh_fields ethtool callbacks.
>
> Note that I'm deleting all the boilerplate kdoc from the affected
> functions in the more recent drivers. If the maintainers feel strongly
> I can respin and add it back, but it really feels useless and undue
> burden for refactoring. No other vendor does this.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/7] eth: igb: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/f148250e357b
- [net-next,v2,2/7] eth: igc: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/575d1b28d204
- [net-next,v2,3/7] eth: ixgbe: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/ecb86e1ff4a3
- [net-next,v2,4/7] eth: fm10k: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/5bd68c191a82
- [net-next,v2,5/7] eth: i40e: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/5a28983710b7
- [net-next,v2,6/7] eth: ice: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/1899fce53a78
- [net-next,v2,7/7] eth: iavf: migrate to new RXFH callbacks
https://git.kernel.org/netdev/net-next/c/2c5f2ad1d919
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: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 18:09 [PATCH net-next v2 0/7] eth: intel: migrate to new RXFH callbacks Jakub Kicinski
2025-06-14 18:09 ` [PATCH net-next v2 1/7] eth: igb: " Jakub Kicinski
2025-06-14 18:09 ` [PATCH net-next v2 2/7] eth: igc: " Jakub Kicinski
2025-06-16 15:23 ` Joe Damato
2025-06-14 18:09 ` [PATCH net-next v2 3/7] eth: ixgbe: " Jakub Kicinski
2025-06-16 15:25 ` Joe Damato
2025-06-14 18:09 ` [PATCH net-next v2 4/7] eth: fm10k: " Jakub Kicinski
2025-06-16 15:27 ` Joe Damato
2025-06-14 18:09 ` [PATCH net-next v2 5/7] eth: i40e: " Jakub Kicinski
2025-06-16 15:30 ` Joe Damato
2025-06-14 18:09 ` [PATCH net-next v2 6/7] eth: ice: " Jakub Kicinski
2025-06-16 15:33 ` Joe Damato
2025-06-14 18:09 ` [PATCH net-next v2 7/7] eth: iavf: " Jakub Kicinski
2025-06-16 15:35 ` Joe Damato
2025-06-16 17:40 ` [PATCH net-next v2 0/7] eth: intel: " Tony Nguyen
2025-06-16 18:25 ` Keller, Jacob E
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=175012445200.2579607.10501400435352945895.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).