All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: 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, anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com, jacob.e.keller@intel.com,
	michal.swiatkowski@linux.intel.com,
	Jakub Kicinski <kuba@kernel.org>
Subject: [Intel-wired-lan] [PATCH net-next 0/7] eth: intel: migrate to new RXFH callbacks
Date: Thu, 12 Jun 2025 18:01:04 -0700	[thread overview]
Message-ID: <20250613010111.3548291-1-kuba@kernel.org> (raw)

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.

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

 .../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  | 20 +++----
 7 files changed, 83 insertions(+), 158 deletions(-)

-- 
2.49.0


WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: 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, anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com, jacob.e.keller@intel.com,
	michal.swiatkowski@linux.intel.com,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/7] eth: intel: migrate to new RXFH callbacks
Date: Thu, 12 Jun 2025 18:01:04 -0700	[thread overview]
Message-ID: <20250613010111.3548291-1-kuba@kernel.org> (raw)

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.

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

 .../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  | 20 +++----
 7 files changed, 83 insertions(+), 158 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-06-13  1:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13  1:01 Jakub Kicinski [this message]
2025-06-13  1:01 ` [PATCH net-next 0/7] eth: intel: migrate to new RXFH callbacks Jakub Kicinski
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 1/7] eth: igb: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  7:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-13  7:49     ` Loktionov, Aleksandr
2025-06-13 12:11   ` Joe Damato
2025-06-13 12:11     ` Joe Damato
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 2/7] eth: igc: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  7:48   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-13  7:48     ` Loktionov, Aleksandr
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 3/7] eth: ixgbe: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  7:48   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-13  7:48     ` Loktionov, Aleksandr
2025-06-13 17:56   ` Jakub Kicinski
2025-06-13 17:56     ` Jakub Kicinski
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 4/7] eth: fm10k: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 5/7] eth: i40e: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  7:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-13  7:49     ` Loktionov, Aleksandr
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 6/7] eth: ice: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  7:50   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-13  7:50     ` Loktionov, Aleksandr
2025-06-13  1:01 ` [Intel-wired-lan] [PATCH net-next 7/7] eth: iavf: " Jakub Kicinski
2025-06-13  1:01   ` Jakub Kicinski
2025-06-13  7:49   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-06-13  7:49     ` Loktionov, Aleksandr

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=20250613010111.3548291-1-kuba@kernel.org \
    --to=kuba@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=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 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.