linux-kernel - Re: [PATCH v3 0/3] SDM670 Global Clocks

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] [day] [month] [year] [list]

Date:   Wed, 14 Sep 2022 22:36:58 -0500
From:   Bjorn Andersson <andersson@...nel.org>
To:     mailingradian@...il.com, linux-arm-msm@...r.kernel.org
Cc:     mturquette@...libre.com, agross@...nel.org, sboyd@...nel.org,
        konrad.dybcio@...ainline.org, jo@...amily.in,
        linux-clk@...r.kernel.org, robh+dt@...nel.org, caleb@...nolly.tech,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        ~postmarketos/upstreaming@...ts.sr.ht,
        krzysztof.kozlowski+dt@...aro.org, tdas@...eaurora.org
Subject: Re: [PATCH v3 0/3] SDM670 Global Clocks

On Thu, 8 Sep 2022 19:12:21 -0400, Richard Acayan wrote:
> Changes since v2:
>  - drop GCC_SDCC1_BCR reset
>  - reorder gcc-sdm845 and gcc-sdm670 if statements in bindings
>  - add space
>  - accumulate review tags
> 
> Changes since v1:
>  - regenerate patches to fixed malformed patch
>  - fix schema so that the parent clocks are specified correctly
>  - remove core_bi_test_pll_se from new parent_data to match array sizes
>  - reference correct frequency table for gcc_sdm670_cpuss_rbcpr_clk_src
>  - set correct index for sdcc1_ice_core_clk_src
> 
> [...]

Applied, thanks!

[1/3] dt-bindings: clock: gcc-sdm845: add sdm670 global clocks
      commit: 657e9326658c1c570eb1e8fd122a4a7936433673
[2/3] clk: qcom: gcc-sdm845: use device tree match data
      commit: 8e90216d2db99f0b883be3b40d5b581437dc4a5d
[3/3] clk: qcom: gcc-sdm845: add sdm670 global clock data
      commit: ae66b1fe48e2dd91229f2b8f25295bce629382d0

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>