From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 1/5] clk: remove duplicated code with __clk_set_parent_after
Date: Thu, 13 Aug 2015 11:25:10 -0700 [thread overview]
Message-ID: <20150813182510.GQ26614@codeaurora.org> (raw)
In-Reply-To: <1438089585-30103-2-git-send-email-aisheng.dong@freescale.com>
On 07/28, Dong Aisheng wrote:
> __clk_set_parent_after() actually used the second argument then we
> could put this duplicate logic in there and call it with a different
> order of arguments in the success vs. error paths in this function.
>
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Dong Aisheng <aisheng.dong@freescale.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-08-13 18:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:19 [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 1/5] clk: remove duplicated code with __clk_set_parent_after Dong Aisheng
2015-08-13 18:25 ` Stephen Boyd [this message]
2015-07-28 13:19 ` [PATCH V3 2/5] clk: introduce clk_core_enable_lock and clk_core_disable_lock functions Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 3/5] clk: move clk_disable_unused after clk_core_disable_unprepare function Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 4/5] clk: core: add CLK_OPS_PARENT_ON flags to support clocks require parent on Dong Aisheng
2015-08-14 1:01 ` Stephen Boyd
2015-08-17 12:45 ` Dong Aisheng
2015-08-19 11:07 ` Dong Aisheng
2015-09-09 9:20 ` Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 5/5] " Dong Aisheng
2015-07-28 14:38 ` [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation Dong Aisheng
2015-08-04 9:45 ` Dong Aisheng
2015-08-13 10:17 ` Dong Aisheng
2016-02-22 14:55 ` Fabio Estevam
2016-02-23 3:45 ` Dong Aisheng
2015-08-13 20:55 ` Joachim Eastwood
2016-03-30 16:00 ` Fabio Estevam
2016-03-31 13:51 ` Dong Aisheng
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=20150813182510.GQ26614@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).