From: Stephen Boyd <sboyd@codeaurora.org>
To: Mike Turquette <mturquette@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Subject: Re: [PATCH v2 3/3] clk: Replace of_clk_get_by_clkspec() with of_clk_get_from_provider()
Date: Wed, 11 Mar 2015 17:35:54 -0700 [thread overview]
Message-ID: <5500DF6A.2090802@codeaurora.org> (raw)
In-Reply-To: <1423251765-2947-4-git-send-email-sboyd@codeaurora.org>
On 02/06/15 11:42, Stephen Boyd wrote:
> of_clk_get_by_clkspec() has the same function signature as
> of_clk_get_from_provider()
>
> struct clk *of_clk_get_by_clkspec(struct of_phandle_args
> *clkspec)
> struct clk *of_clk_get_from_provider(struct of_phandle_args
> *clkspec)
>
> except of_clk_get_by_clkspec() checks to make sure clkspec is not
> NULL. Let's remove of_clk_get_by_clkspec() and replace the
> callers of it (clkconf.c) with of_clk_get_from_provider().
>
> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-03-12 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 19:42 [PATCH v2 0/3] CCF fixes/cleanup for per-user series Stephen Boyd
2015-02-06 19:42 ` [PATCH v2 1/3] clkdev: Always allocate a struct clk and call __clk_get() w/ CCF Stephen Boyd
2015-02-11 3:08 ` Mike Turquette
2015-02-06 19:42 ` [PATCH v2 2/3] clk: Rename child_node to clks_node to avoid confusion Stephen Boyd
2015-03-12 0:35 ` Stephen Boyd
2015-02-06 19:42 ` [PATCH v2 3/3] clk: Replace of_clk_get_by_clkspec() with of_clk_get_from_provider() Stephen Boyd
2015-03-12 0:35 ` Stephen Boyd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5500DF6A.2090802@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=tomeu.vizoso@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox