Hello Varun,

Patch 1 should be in LTS, as it corrects a compilation issue when
enabling DECRYPTION_SUPPORT.

The other ones correct sparse tool warnings, so I'm not sure they fit
with LTS criteria.
That said, patch 2 & 4, by adding static to functions, reduce their
scopes, so may be seen as security patches.
Patch 3 shouldn't go to LTS.


Best regards,
Yann

On 1/19/23 12:58, Varun Wadekar wrote:
> Hello ST maintainers,
>
> Hope you are doing well.
>
> The merge window for the next LTS release is now open. We are collecting
> changes for the release and need your input.
>
> Can you please help us decide if the following patches should be part of
> the LTS release?
>
>  1. 377846b65 fix(st): include utils.h to solve compilation error
>  2. d1d8a9bad fix(st): make metadata_block_spec static
>  3. 6e55f9e2c fix(stm32mp1): add missing platform.h include
>  4. 70a422ba8 fix(st-crypto): set get_plain_pk_from_asn1() static
>
> Thanks.
>
>
> _______________________________________________
> TF-A LTS mailing list -- tfa-lts@lists.trustedfirmware.org
> To unsubscribe send an email to tfa-lts-leave@lists.trustedfirmware.org