From: Stephen Boyd <sboyd@codeaurora.org>
To: Mike Turquette <mturquette@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-kernel@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Alban Browaeys <alban.browaeys@gmail.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: [PATCH v2 0/3] CCF fixes/cleanup for per-user series
Date: Fri, 6 Feb 2015 11:42:42 -0800 [thread overview]
Message-ID: <1423251765-2947-1-git-send-email-sboyd@codeaurora.org> (raw)
Here are some fixes from yesterdays's dive into the fallout from the
per-user constraints patches. We should do a final sweep later
to rename local variables with type struct clk_core to core.
Changes from v1:
* Picked up tags
* Dropped clk.h include in last patch
* Handled IS_ERR() retrurn from __clk_create_clk() in clkdev in first patch
* Removed dead comment in last patch
Stephen Boyd (3):
clkdev: Always allocate a struct clk and call __clk_get() w/ CCF
clk: Rename child_node to clks_node to avoid confusion
clk: Replace of_clk_get_by_clkspec() with of_clk_get_from_provider()
drivers/clk/clk-conf.c | 7 +++---
drivers/clk/clk.c | 60 +++++++++++++++++++++++++++-----------------------
drivers/clk/clk.h | 22 ++++++++++++++----
drivers/clk/clkdev.c | 57 ++++++++++-------------------------------------
4 files changed, 66 insertions(+), 80 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2015-02-06 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 19:42 Stephen Boyd [this message]
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
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=1423251765-2947-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alban.browaeys@gmail.com \
--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