Subject: [PATCH RFC v1 3/5] clk: remove unneeded __clk_enable and __clk_disable

From: [email-masked] (Stephen Boyd)
Date: Thu, 30 Apr 2015 12:09:18 -0700

On 04/15/15 07:26, Dong Aisheng wrote:
> The only thing __clk_enable/__clk_disable does is NULL pointer checking
> of clk except calling clk_core_{enable|disable} which is already handled
> by clk_core_{enable|disable}.
> So remove this unneeded function.
>
> Cc: Mike Turquette <[email-masked]>
> Cc: Stephen Boyd <[email-masked]>
> Signed-off-by: Dong Aisheng <[email-masked]>
> ---

No. You can call clk_enable() and clk_disable() with NULL and it should
be a no-op. With this change it would cause a NULL pointer exception.

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