linux-kernel - Re: [PATCH v2 2/3] clk: Add __clk_hw_set

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]

Message-ID: <54DD0524.4060503@codeaurora.org>
Date:	Thu, 12 Feb 2015 11:55:16 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	Mike Turquette <mturquette@...aro.org>
CC:	Tomeu Vizoso <tomeu.vizoso@...labora.com>,
	Emilio López 
	<emilio@...pez.com.ar>,
	Peter De Schrijver <pdeschrijver@...dia.com>,
	Robert Jarzmik <robert.jarzmik@...e.fr>,
	Giuseppe Cavallaro <peppe.cavallaro@...com>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/3] clk: Add __clk_hw_set_clk helper function

On 02/12/15 05:58, Javier Martinez Canillas wrote:
> After the clk API change to return a per-user clock instance, both the
> struct clk_core and struct clk pointers from the hw clock needs to be
> assigned to clock that share the same state.
>
> In the future the struct clk_core will be removed and this is going to

s/clk_core/clk/?

> change again so to avoid having to change the assignments twice in all
> the drivers, add a helper function to have an indirection level.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
> ---

Reviewed-by: Stephen Boyd <sboyd@...eaurora.org>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/