netdev - Re: [PATCH net-next] eth: gianfar: migrate to new RXFH callbacks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <175012445574.2579607.7186602700396760158.git-patchwork-notify@kernel.org>
Date: Tue, 17 Jun 2025 01:40:55 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
 claudiu.manoil@....com
Subject: Re: [PATCH net-next] eth: gianfar: migrate to new RXFH callbacks

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Fri, 13 Jun 2025 10:27:51 -0700 you wrote:
> Migrate to new callbacks added by commit 9bb00786fc61 ("net: ethtool:
> add dedicated callbacks for getting and setting rxfh fields").
> 
> Uniquely, this driver supports only the SET operation. It does not
> support GET at all. The SET callback also always returns 0, even
> tho it checks a bunch of conditions, and if my quick reading is
> right, expects the user to insert filtering rules for given flow
> type first? Long story short it seems too convoluted to easily
> add the GET as part of the conversion.
> 
> [...]

Here is the summary with links:
  - [net-next] eth: gianfar: migrate to new RXFH callbacks
    https://git.kernel.org/netdev/net-next/c/3b5b1c428260

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html