On Thu Sep 19, 2024 at 8:57 AM EEST, tzungbi wrote:
> From: Tzung-Bi Shih <[email protected]>
>
> These are Google Security Chip drivers and are mostly used for ChromeOS
> platforms.  Add a new entry for them.
>
> Signed-off-by: Tzung-Bi Shih <[email protected]>
> ---
>  MAINTAINERS | 9 +++++++++
>  1 file changed, 9 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8a76c256229c..07dc83e01216 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9593,6 +9593,15 @@ S:     Maintained
>  T:   git 
> git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
>  F:   drivers/firmware/google/
>  
> +GOOGLE SECURITY CHIP DRIVERS
> +M:   Tzung-Bi Shih <[email protected]>
> +R:   Andrey Pronin <[email protected]>
> +L:   [email protected]
> +S:   Maintained
> +T:   git 
> git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
> +F:   Documentation/devicetree/bindings/tpm/google,cr50.yaml
> +F:   drivers/char/tpm/*cr50*
> +
>  GOOGLE TENSOR SoC SUPPORT
>  M:   Peter Griffin <[email protected]>
>  L:   [email protected] (moderated for non-subscribers)

1. From now I expect either give reviewed-by. That helps also with my
   decision so I welcome that of course.
2. In the end I pick drivers/char/tpm changes. This not because I would
   want to cr50 specific changes but because I want to make sure that
   they fit to the context.

With those constraints:

Reviewed-by: Jarkko Sakkinen <[email protected]>

BR, Jarkko

Reply via email to