| 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: <165580921308.31228.13702816292923701377.git-patchwork-notify@kernel.org>
Date: Tue, 21 Jun 2022 11:00:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Simon Horman <simon.horman@...igine.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
netdev@...r.kernel.org, oss-drivers@...igine.com,
yu.xiao@...igine.com
Subject: Re: [PATCH net-next] nfp: compose firmware file name with new hwinfo
"nffw.partno"
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@...hat.com>:
On Mon, 20 Jun 2022 12:39:12 +0200 you wrote:
> From: Yu Xiao <yu.xiao@...igine.com>
>
> During initialization of the NFP driver, a file name for loading
> application firmware is composed using the NIC's AMDA information and port
> type (count and speed). E.g.: "nic_AMDA0145-1012_2x10.nffw".
>
> In practice there may be many variants for each NIC type, and many of the
> variants relate to assembly components which do not concern the driver and
> application firmware implementation. Yet the current scheme leads to a
> different application firmware file name for each variant, because they
> have different AMDA information.
>
> [...]
Here is the summary with links:
- [net-next] nfp: compose firmware file name with new hwinfo "nffw.partno"
https://git.kernel.org/netdev/net-next/c/00bb2920cf6a
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