From: patchwork-bot+netdevbpf@kernel.org
To: Manish Chopra <manishc@marvell.com>
Cc: kuba@kernel.org, pmenzel@molgen.mpg.de, netdev@vger.kernel.org,
aelior@marvell.com, regressions@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH net] bnx2x: fix built-in kernel driver load failure
Date: Thu, 17 Mar 2022 16:40:11 +0000 [thread overview]
Message-ID: <164753521133.23544.8557619135269165608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220316214613.6884-1-manishc@marvell.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Mar 2022 14:46:13 -0700 you wrote:
> commit b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0")
> added request_firmware() logic in probe() which caused
> built-in kernel driver (CONFIG_BNX2X=y) load failure (below),
> as access to firmware file is not feasible during the probe.
>
> "Direct firmware load for bnx2x/bnx2x-e2-7.13.21.0.fw
> failed with error -2"
>
> [...]
Here is the summary with links:
- [net] bnx2x: fix built-in kernel driver load failure
https://git.kernel.org/netdev/net/c/424e7834e293
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:[~2022-03-17 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 21:46 [PATCH net] bnx2x: fix built-in kernel driver load failure Manish Chopra
2022-03-17 7:32 ` Paul Menzel
2022-03-17 9:55 ` [EXT] " Manish Chopra
2022-03-17 13:31 ` Paul Menzel
2022-03-17 15:33 ` Jakub Kicinski
2022-03-17 16:28 ` Paul Menzel
2022-03-17 16:40 ` 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=164753521133.23544.8557619135269165608.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aelior@marvell.com \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).