From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX clock driver update for 4.6
Date: Tue, 1 Mar 2016 17:43:40 -0800 [thread overview]
Message-ID: <20160302014340.GE24999@codeaurora.org> (raw)
In-Reply-To: <20160229080607.GT22051@tiger>
On 02/29, Shawn Guo wrote:
> Hi Mike, Stephen,
>
> The following are the i.MX clock patches I queued for 4.6. Please pull
> and keep it stable, as I need to pull it into my DT branch to resolve
> the dependency on those new clock IDs.
>
> Thanks,
> Shawn
>
>
> The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
>
> Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-4.6
>
> for you to fetch changes up to f6c3aec2f7a218abec9e5c00353abc02224be49e:
>
> clk: imx: add kpp clock for i.MX6UL (2016-02-28 10:45:29 +0800)
Thanks. Pulled.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-03-02 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 8:06 [GIT PULL] i.MX clock driver update for 4.6 Shawn Guo
2016-03-02 1:43 ` 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=20160302014340.GE24999@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).