linux-kernel - Re: [PATCH v10 26/33] clk: rk3399: use proper crypto0 name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 28 Sep 2022 11:58:30 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Corentin Labbe <clabbe@...libre.com>, ardb@...nel.org,
        davem@...emloft.net, heiko@...ech.de, herbert@...dor.apana.org.au,
        krzysztof.kozlowski+dt@...aro.org, mturquette@...libre.com,
        robh+dt@...nel.org
Cc:     linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-crypto@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
        Corentin Labbe <clabbe@...libre.com>,
        Rob Herring <robh@...nel.org>
Subject: Re: [PATCH v10 26/33] clk: rk3399: use proper crypto0 name

Quoting Corentin Labbe (2022-09-27 00:55:04)
> RK3399 has 2 crypto instance, named crypto0 and crypto1 in the TRM.
> Only reset for crypto1 is correctly named, but crypto0 is not.
> Since nobody use them , add a 0 to be consistent with the TRM and crypto1 entries.
> 
> Acked-by: Rob Herring <robh@...nel.org>
> Signed-off-by: Corentin Labbe <clabbe@...libre.com>
> ---

Acked-by: Stephen Boyd <sboyd@...nel.org>