From: patchwork-bot+netdevbpf@kernel.org
To: Gal Pressman <gal@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
andrew@lunn.ch, horms@kernel.org, dtatulea@nvidia.com
Subject: Re: [PATCH net-next v2] ethtool: Don't check for RXFH fields conflict when no input_xfrm is requested
Date: Wed, 16 Jul 2025 22:10:10 +0000 [thread overview]
Message-ID: <175270381000.1341865.15234146068113913299.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250715140754.489677-1-gal@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Jul 2025 17:07:54 +0300 you wrote:
> The requirement of ->get_rxfh_fields() in ethtool_set_rxfh() is there to
> verify that we have no conflict of input_xfrm with the RSS fields
> options, there is no point in doing it if input_xfrm is not
> supported/requested.
>
> This is under the assumption that a driver that supports input_xfrm will
> also support ->get_rxfh_fields(), so add a WARN_ON() to
> ethtool_check_ops() to verify it, and remove the op NULL check.
>
> [...]
Here is the summary with links:
- [net-next,v2] ethtool: Don't check for RXFH fields conflict when no input_xfrm is requested
https://git.kernel.org/netdev/net-next/c/410b0ace8891
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-07-16 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 14:07 [PATCH net-next v2] ethtool: Don't check for RXFH fields conflict when no input_xfrm is requested Gal Pressman
2025-07-16 22:10 ` 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=175270381000.1341865.15234146068113913299.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.