From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX clock updates for 4.7
Date: Fri, 15 Apr 2016 15:44:01 -0700 [thread overview]
Message-ID: <20160415224401.GW14441@codeaurora.org> (raw)
In-Reply-To: <20160413072001.GM28903@tiger>
On 04/13, Shawn Guo wrote:
> Hi Mike, Stephen,
>
> Please pull the following i.MX clock updates I queued for 4.7, and keep
> the branch stable. Thanks.
>
> Shawn
>
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
>
> Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-clk-4.7
>
> for you to fetch changes up to 69c542e8022ca53c5fee664548163809eb1777c3:
>
> clk: imx: vf610: fix whitespace in vf610-clock.h (2016-04-12 09:31:08 +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-04-15 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 7:20 [GIT PULL] i.MX clock updates for 4.7 Shawn Guo
2016-04-15 22:44 ` 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=20160415224401.GW14441@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).