| 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
| ||
|
Message-Id:
<176244060675.238839.11553624450020733973.git-patchwork-notify@kernel.org>
Date: Thu, 06 Nov 2025 14:50:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, andrew+netdev@...n.ch, netdev@...r.kernel.org,
madhu.chittim@...el.com, aleksander.lobakin@...el.com, horms@...nel.org,
bhelgaas@...gle.com, linux-pci@...r.kernel.org, sridhar.samudrala@...el.com,
aleksandr.loktionov@...el.com, marek.landowski@...el.com
Subject: Re: [PATCH net-next] idpf: add support for IDPF PCI programming
interface
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Mon, 3 Nov 2025 14:46:30 -0800 you wrote:
> From: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
>
> At present IDPF supports only 0x1452 and 0x145C as PF and VF device IDs
> on our current generation hardware. Future hardware exposes a new set of
> device IDs for each generation. To avoid adding a new device ID for each
> generation and to make the driver forward and backward compatible,
> make use of the IDPF PCI programming interface to load the driver.
>
> [...]
Here is the summary with links:
- [net-next] idpf: add support for IDPF PCI programming interface
https://git.kernel.org/netdev/net-next/c/13068e9d5726
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists