From: Stephen Boyd <sboyd@codeaurora.org>
To: Dong Aisheng <aisheng.dong@nxp.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
broonie@kernel.org, yibin.gong@nxp.com, rjw@rjwysocki.net,
viresh.kumar@linaro.org, mturquette@baylibre.com,
shawnguo@kernel.org, fabio.estevam@nxp.com, anson.huang@nxp.com,
ping.bai@nxp.com, leonard.crestez@nxp.com,
octavian.purdila@nxp.com, linux@armlinux.org.uk,
geert@linux-m68k.org, f.fainelli@gmail.com, dongas86@gmail.com
Subject: Re: [PATCH V3 0/3] clk: introduce clk_bulk_get accessories
Date: Fri, 2 Jun 2017 15:40:34 -0700 [thread overview]
Message-ID: <20170602224034.GX20170@codeaurora.org> (raw)
In-Reply-To: <1495201746-31841-1-git-send-email-aisheng.dong@nxp.com>
On 05/19, Dong Aisheng wrote:
> These helper function allows drivers to get several clk consumers in
> one operation. If any of the clk cannot be acquired then any clks
> that were got will be put before returning to the caller.
>
I've merged the first two into a stable branch and merged to
clk-next. The third one can go via cpufreq.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-02 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 13:49 [PATCH V3 0/3] clk: introduce clk_bulk_get accessories Dong Aisheng
2017-05-19 13:49 ` [PATCH V3 1/3] clk: add " Dong Aisheng
2017-06-02 22:39 ` Stephen Boyd
2017-05-19 13:49 ` [PATCH V3 2/3] clk: add managed version of clk_bulk_get Dong Aisheng
2017-06-02 22:39 ` Stephen Boyd
2017-05-19 13:49 ` [PATCH V3 3/3] cpufreq: imx6q: refine clk operations Dong Aisheng
2017-06-02 22:40 ` Stephen Boyd [this message]
2017-06-13 9:18 ` [PATCH V3 0/3] clk: introduce clk_bulk_get accessories 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=20170602224034.GX20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=broonie@kernel.org \
--cc=dongas86@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=geert@linux-m68k.org \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=octavian.purdila@nxp.com \
--cc=ping.bai@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yibin.gong@nxp.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;
as well as URLs for NNTP newsgroup(s).