From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <edumazet@google.com>,
<pabeni@redhat.com>, <andrew+netdev@lunn.ch>, <horms@kernel.org>,
<intel-wired-lan@lists.osuosl.org>,
<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: Mon, 16 Jun 2025 10:40:18 -0700 [thread overview]
Message-ID: <3c8f1154-91cd-4b25-b517-30c4cb97f40b@intel.com> (raw)
In-Reply-To: <20250614180907.4167714-1-kuba@kernel.org>
On 6/14/2025 11:09 AM, Jakub Kicinski 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.
>
> v2:
> - fix missing change to ops struct in ixgbe
> v1: https://lore.kernel.org/20250613010111.3548291-1-kuba@kernel.org
>
> Jakub Kicinski (7):
> eth: igb: migrate to new RXFH callbacks
> eth: igc: migrate to new RXFH callbacks
> eth: ixgbe: migrate to new RXFH callbacks
> eth: fm10k: migrate to new RXFH callbacks
> eth: i40e: migrate to new RXFH callbacks
> eth: ice: migrate to new RXFH callbacks
> eth: iavf: migrate to new RXFH callbacks
For the series:
Reviewed-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> .../net/ethernet/intel/fm10k/fm10k_ethtool.c | 34 ++++-------
> .../net/ethernet/intel/i40e/i40e_ethtool.c | 38 +++++-------
> .../net/ethernet/intel/iavf/iavf_ethtool.c | 52 ++++------------
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 59 ++++++-------------
> drivers/net/ethernet/intel/igb/igb_ethtool.c | 20 +++----
> drivers/net/ethernet/intel/igc/igc_ethtool.c | 18 +++---
> .../net/ethernet/intel/ixgbe/ixgbe_ethtool.c | 22 +++----
> 7 files changed, 85 insertions(+), 158 deletions(-)
>
next prev parent reply other threads:[~2025-06-16 17: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 ` Tony Nguyen [this message]
2025-06-16 18:25 ` [PATCH net-next v2 0/7] eth: intel: " Keller, Jacob E
2025-06-17 1:40 ` patchwork-bot+netdevbpf
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=3c8f1154-91cd-4b25-b517-30c4cb97f40b@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=andrew+netdev@lunn.ch \
--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).