From: Stephen Boyd <sboyd@codeaurora.org>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Mike Turquette <mturquette@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>
Subject: Re: [PATCH 3/3] clk: Replace of_clk_get_by_clkspec() with of_clk_get_from_provider()
Date: Fri, 06 Feb 2015 09:24:13 -0800 [thread overview]
Message-ID: <54D4F8BD.5090400@codeaurora.org> (raw)
In-Reply-To: <54D4A8C9.9000507@collabora.com>
On 02/06/15 03:43, Tomeu Vizoso wrote:
> On 02/06/2015 01:19 AM, Stephen Boyd wrote:
>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>> index 315dc22b7356..5d804a43ab1a 100644
>> --- a/drivers/clk/clk.c
>> +++ b/drivers/clk/clk.c
>> @@ -2807,16 +2807,6 @@ static LIST_HEAD(of_clk_providers);
>> static DEFINE_MUTEX(of_clk_mutex);
>>
>> /* of_clk_provider list locking helpers */
> Patch looks good to me, but this comment can be removed now.
>
> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>
Done, plus I removed "clk.h" include in clk-conf.c.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-02-06 17:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 0:19 [PATCH 0/3] CCF fixes/cleanup for per-user series Stephen Boyd
2015-02-06 0:19 ` [PATCH 1/3] clkdev: Always allocate a struct clk and call __clk_get() w/ CCF Stephen Boyd
2015-02-06 0:36 ` Stephen Boyd
2015-02-06 0:19 ` [PATCH 2/3] clk: Rename child_node to clks_node to avoid confusion Stephen Boyd
2015-02-06 14:02 ` Tomeu Vizoso
2015-02-06 0:19 ` [PATCH 3/3] clk: Replace of_clk_get_by_clkspec() with of_clk_get_from_provider() Stephen Boyd
2015-02-06 11:43 ` Tomeu Vizoso
2015-02-06 17:24 ` Stephen Boyd [this message]
2015-02-06 1:40 ` [PATCH v2] clkdev: Always allocate a struct clk and call __clk_get() w/ CCF Stephen Boyd
2015-02-06 10:57 ` Sylwester Nawrocki
2015-02-06 11:23 ` Tomeu Vizoso
2015-02-06 17:36 ` Stephen Boyd
2015-02-06 12:34 ` Tomeu Vizoso
2015-02-06 17:11 ` Stephen Boyd
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=54D4F8BD.5090400@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
Powered by JetHome