| 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:
<170228942357.26769.14270472436980157327.git-patchwork-notify@kernel.org>
Date: Mon, 11 Dec 2023 10:10:23 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Shinas Rasheed <srasheed@...vell.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, hgani@...vell.com,
vimleshk@...vell.com, egallen@...hat.com, mschmidt@...hat.com,
pabeni@...hat.com, horms@...nel.org, kuba@...nel.org, davem@...emloft.net,
wizhao@...hat.com, konguyen@...hat.com, vburru@...vell.com,
sedara@...vell.com, edumazet@...gle.com, aayarekar@...vell.com,
sburla@...vell.com
Subject: Re: [PATCH net v3] octeon_ep: explicitly test for firmware ready value
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:
On Thu, 7 Dec 2023 21:56:46 -0800 you wrote:
> The firmware ready value is 1, and get firmware ready status
> function should explicitly test for that value. The firmware
> ready value read will be 2 after driver load, and on unbind
> till firmware rewrites the firmware ready back to 0, the value
> seen by driver will be 2, which should be regarded as not ready.
>
> Fixes: 10c073e40469 ("octeon_ep: defer probe if firmware not ready")
> Signed-off-by: Shinas Rasheed <srasheed@...vell.com>
>
> [...]
Here is the summary with links:
- [net,v3] octeon_ep: explicitly test for firmware ready value
https://git.kernel.org/netdev/net/c/284f71762241
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