Messages in this thread | | | Date | Fri, 17 Nov 2023 15:06:44 +0100 | From | Andrew Lunn <> | Subject | Re: [PATCH] firmware_loader: Expand Firmware upload error codes with firmware invalid error |
| |
On Fri, Nov 17, 2023 at 08:45:59AM -0500, Greg Kroah-Hartman wrote: > On Fri, Nov 17, 2023 at 11:27:53AM +0100, Kory Maincent 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 > > > > Acked-by: Luis Chamberlain <mcgrof@kernel.org> > > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com> > > --- > > > > This patch was initially submitted as part of a net patch series. > > Conor expressed interest in using it in a different subsystem. > > Consequently, I extracted it from the series and submitted it separately > > to the main tree, driver-core. > > https://lore.kernel.org/netdev/20231116-feature_poe-v1-7-be48044bf249@bootlin.com/ > > So you want me to take it through my tree? Sure, but if you are relying > on this for any other code, it will be a while before it gets into > Linus's tree, not until 6.8-rc1, is that ok?
My idea was that you could create a stable branch, which can then be pulled into netdev and arm-soc.
If you don't want to do that, we can ask Arnd to take it, and he can create a stable branch which we pull into netdev.
Andrew
| |