[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023111720-slicer-exes-7d9f@gregkh>
Date: Fri, 17 Nov 2023 08:45:59 -0500
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Luis Chamberlain <mcgrof@...nel.org>,
Russ Weight <russ.weight@...ux.dev>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-kernel@...r.kernel.org, Conor Dooley <conor@...nel.org>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: [PATCH] firmware_loader: Expand Firmware upload error codes with
firmware invalid error
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@...nel.org>
> Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Signed-off-by: Kory Maincent <kory.maincent@...tlin.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?
thanks,
greg k-h
Powered by blists - more mailing lists