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>,
<bharat@chelsio.com>, <benve@cisco.com>, <satishkh@cisco.com>,
<claudiu.manoil@nxp.com>, <vladimir.oltean@nxp.com>,
<wei.fang@nxp.com>, <xiaoning.wang@nxp.com>,
<przemyslaw.kitszel@intel.com>, <bryan.whitehead@microchip.com>,
<ecree.xilinx@gmail.com>, <rosenp@gmail.com>,
<imx@lists.linux.dev>, "Joe Damato" <joe@dama.to>
Subject: Re: [PATCH net-next v2 4/5] eth: e1000e: migrate to new RXFH callbacks
Date: Mon, 16 Jun 2025 11:07:31 -0700 [thread overview]
Message-ID: <10b4c1d0-2f96-48ac-b218-a701d027afc2@intel.com> (raw)
In-Reply-To: <20250614180638.4166766-5-kuba@kernel.org>
On 6/14/2025 11:06 AM, Jakub Kicinski wrote:
> Migrate to new callbacks added by commit 9bb00786fc61 ("net: ethtool:
> add dedicated callbacks for getting and setting rxfh fields").
> This driver's RXFH config is read only / fixed and it's the only
> get_rxnfc sub-command the driver supports. So convert the get_rxnfc
> handler into a get_rxfh_fields handler.
>
> Reviewed-by: Joe Damato <joe@dama.to>
Reviewed-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2025-06-16 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 18:06 [PATCH net-next v2 0/5] eth: migrate to new RXFH callbacks (get-only drivers) Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 1/5] eth: cisco: migrate to new RXFH callbacks Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 2/5] eth: cxgb4: " Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 3/5] eth: lan743x: " Jakub Kicinski
2025-06-14 18:06 ` [PATCH net-next v2 4/5] eth: e1000e: " Jakub Kicinski
2025-06-16 18:07 ` Tony Nguyen [this message]
2025-06-14 18:06 ` [PATCH net-next v2 5/5] eth: enetc: " Jakub Kicinski
2025-06-15 7:41 ` Joe Damato
2025-06-16 1:32 ` Wei Fang
2025-06-17 1:40 ` [PATCH net-next v2 0/5] eth: migrate to new RXFH callbacks (get-only drivers) 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=10b4c1d0-2f96-48ac-b218-a701d027afc2@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=benve@cisco.com \
--cc=bharat@chelsio.com \
--cc=bryan.whitehead@microchip.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=imx@lists.linux.dev \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rosenp@gmail.com \
--cc=satishkh@cisco.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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