APPLIED: [SRU][J:linux-bluefield][PATCH v1 0/1] mlxbf-bootctl: fails to report info about cards using dev keys

[Bartlomiej Zolnierkiewicz]

Applied to jammy:linux-bluefield/master-next. Thanks.

--
Best regards,
Bartlomiej

On Thu, Dec 7, 2023 at 6:08 PM David Thompson <davthompson at nvidia.com> wrote:
>
> BugLink: https://bugs.launchpad.net/bugs/2045919
>
> SRU Justification:
>
> [Impact]
>
> There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
> report when a secure boot enabled card is using development keys. The program
> will instead report lifecycle state as "GA Secured" which is misleading.
>
> [Fix]
>
> Bring in the following upstream commit from linux-next:
>   "mlxbf-bootctl: correctly identify secure boot with development keys"
>
> [Test Case]
>
> Enable secure boot on a BF3 card that is using development keys
> Login as root on BF3
> Run the command "mlxbf-bootctl"
> Verify that the "lifecycle state" row shows "Secured (development)"
>
> [Regression Potential]
>
> Low risk change, cherry pick of upstream approved commit
>
> David Thompson (1):
>   mlxbf-bootctl: correctly identify secure boot with development keys
>
>  drivers/platform/mellanox/mlxbf-bootctl.c | 39 +++++++++++++++--------
>  1 file changed, 26 insertions(+), 13 deletions(-)
>