From: Stephen Boyd <sboyd@codeaurora.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [GIT PULL] rockchip clock changes for 4.9 part 1
Date: Tue, 6 Sep 2016 18:17:37 -0700 [thread overview]
Message-ID: <20160907011737.GU12510@codeaurora.org> (raw)
In-Reply-To: <2115968.yvb8ppzjmL@phil>
On 09/06, Heiko Stuebner wrote:
> Hi Mike, Stephen,
>
> please find below the pull request with main Rockchip-releated clock
> changes for 4.9.
>
> The signed tag should hopefully explain the contents sufficiently,
> so if nothing stands out please pull.
>
> On the matter of critical clocks, I'm still hoping for the handover type
> to materialize soonish and am hoping of doing the conversion in one go,
> instead of making everything critical now and then having to go through
> the list yet again.
Hmm... ok it sounds like we should look into finishing that off
then. I can't seem to recall why we didn't merge the handoff part
though so I'll have to go look back on that.
>
> Thanks
> Heiko
>
>
> The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
>
> Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v4.9-rockchip-clk1
>
> for you to fetch changes up to 7b0f9e357ac838f640b10fb3db1ac35d9a5fa8de:
>
> clk: rockchip: use the dclk_vop_frac clock ids on rk3399 (2016-09-04 23:48:19 +0200)
Pulled, thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-09-07 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 15:28 [GIT PULL] rockchip clock changes for 4.9 part 1 Heiko Stuebner
2016-09-07 1:17 ` 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=20160907011737.GU12510@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=heiko@sntech.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.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).