From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?K=C3=B6ry_Maincent_=3Ckory=2Emaincent=40bootlin=2Ecom=3E?=@ci.codeaurora.org
Cc: kuba@kernel.org, mcgrof@kernel.org, russ.weight@linux.dev,
gregkh@linuxfoundation.org, rafael@kernel.org,
thomas.petazzoni@bootlin.com, linux-kernel@vger.kernel.org,
conor@kernel.org, andrew@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] firmware_loader: Expand Firmware upload error codes with firmware invalid error
Date: Sat, 25 Nov 2023 03:30:26 +0000 [thread overview]
Message-ID: <170088302600.4689.10780084312021094522.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231122-feature_firmware_error_code-v3-1-04ec753afb71@bootlin.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 22 Nov 2023 14:52:43 +0100 you wrote:
> No error code are available to signal an invalid firmware content.
> Drivers that can check the firmware content validity can not return this
> specific failure to the user-space
>
> Expand the firmware error code with an additional code:
> - "firmware invalid" code which can be used when the provided firmware
> is invalid
>
> [...]
Here is the summary with links:
- [net-next,v3] firmware_loader: Expand Firmware upload error codes with firmware invalid error
https://git.kernel.org/netdev/net-next/c/a066f906ba39
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:[~2023-11-25 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 13:52 [PATCH net-next v3] firmware_loader: Expand Firmware upload error codes with firmware invalid error Kory Maincent
2023-11-24 16:48 ` Simon Horman
2023-11-25 3:24 ` Jakub Kicinski
2023-11-27 18:35 ` Köry Maincent
2023-12-06 12:04 ` Conor Dooley
2023-12-06 15:47 ` Jakub Kicinski
2023-11-25 3:30 ` 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=170088302600.4689.10780084312021094522.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?K=C3=B6ry_Maincent_=3Ckory=2Emaincent=40bootlin=2Ecom=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=conor@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=thomas.petazzoni@bootlin.com \
/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