linux-kernel - Re: [PATCH v1] clk: qcom: Make common clk

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]

Message-ID: <155082283660.77512.10059723735671016353@swboyd.mtv.corp.google.com>
Date:   Fri, 22 Feb 2019 00:07:16 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Jeffrey Hugo <jhugo@...eaurora.org>, bjorn.andersson@...aro.org,
        mturquette@...libre.com
Cc:     marc.w.gonzalez@...e.fr, andy.gross@...aro.org,
        david.brown@...aro.org, linux-arm-msm@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
        Jeffrey Hugo <jhugo@...eaurora.org>
Subject: Re: [PATCH v1] clk: qcom: Make common clk_hw registrations

Quoting Jeffrey Hugo (2019-02-10 12:14:05)
> Several clock controller drivers define a list of clk_hw devices, and then
> register those devices in probe() before using common code to process the
> rest of initialization.  Extend the common code to accept a list of clk_hw
> devices to process, thus eliminating many duplicate implementations.
> 
> Signed-off-by: Jeffrey Hugo <jhugo@...eaurora.org>
> ---

Applied to clk-next