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
Subject: Re: [Intel-wired-lan] [PATCH net-next 3/7] eth: ixgbe: migrate to new RXFH callbacks
Date: Fri, 13 Jun 2025 10:56:08 -0700 [thread overview]
Message-ID: <20250613105608.7eed2f13@kernel.org> (raw)
In-Reply-To: <20250613010111.3548291-4-kuba@kernel.org>
On Thu, 12 Jun 2025 18:01:07 -0700 Jakub Kicinski wrote:
> @@ -3797,6 +3795,8 @@ static const struct ethtool_ops ixgbe_ethtool_ops_e610 = {
> .get_rxfh_key_size = ixgbe_get_rxfh_key_size,
> .get_rxfh = ixgbe_get_rxfh,
> .set_rxfh = ixgbe_set_rxfh,
> + .get_rxfh_fields = ixgbe_get_rxfh_fields,
> + .set_rxfh_fields = ixgbe_set_rxfh_fields,
> .get_eee = ixgbe_get_eee,
> .set_eee = ixgbe_set_eee,
> .get_channels = ixgbe_get_channels,
same bug here as in enetc -- there is another ops struct that needs to
be updated.
--
pw-bot: cr
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
Subject: Re: [PATCH net-next 3/7] eth: ixgbe: migrate to new RXFH callbacks
Date: Fri, 13 Jun 2025 10:56:08 -0700 [thread overview]
Message-ID: <20250613105608.7eed2f13@kernel.org> (raw)
In-Reply-To: <20250613010111.3548291-4-kuba@kernel.org>
On Thu, 12 Jun 2025 18:01:07 -0700 Jakub Kicinski wrote:
> @@ -3797,6 +3795,8 @@ static const struct ethtool_ops ixgbe_ethtool_ops_e610 = {
> .get_rxfh_key_size = ixgbe_get_rxfh_key_size,
> .get_rxfh = ixgbe_get_rxfh,
> .set_rxfh = ixgbe_set_rxfh,
> + .get_rxfh_fields = ixgbe_get_rxfh_fields,
> + .set_rxfh_fields = ixgbe_set_rxfh_fields,
> .get_eee = ixgbe_get_eee,
> .set_eee = ixgbe_set_eee,
> .get_channels = ixgbe_get_channels,
same bug here as in enetc -- there is another ops struct that needs to
be updated.
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-13 17:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 1:01 [Intel-wired-lan] [PATCH net-next 0/7] eth: intel: migrate to new RXFH callbacks Jakub Kicinski
2025-06-13 1:01 ` 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 [this message]
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=20250613105608.7eed2f13@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.