From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Clk Updates for v3.18
Date: Fri, 12 Sep 2014 10:23:47 +0900 [thread overview]
Message-ID: <cover.1410484748.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these second round of Renesas ARM based SoC clk updates for v3.18.
This pull request is based on the previous round of
such requests, tagged as renesas-clk-for-v3.18,
which you have already pulled.
I am taking this change through my tree with Mike's Ack
as it seems to be a smooth way to handle things.
The following changes since commit 8de078f189da45453d2ed2a04288e329cc169731:
clk: shmobile: Add r8a7794 support (2014-08-27 08:40:54 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-clk2-for-v3.18
for you to fetch changes up to b32c44b93af31e9163514df0f3ac2791972eb124:
clk: shmobile: Add r8a7740, sh73a0 SoCs to MSTP bindings (2014-09-10 09:08:10 +0900)
----------------------------------------------------------------
Second Round of Renesas ARM Based SoC Clk Updates for v3.18
* Add r8a7740, sh73a0 SoCs to MSTP bindings
----------------------------------------------------------------
Ulrich Hecht (1):
clk: shmobile: Add r8a7740, sh73a0 SoCs to MSTP bindings
Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2014-09-12 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 1:23 Simon Horman [this message]
2014-09-12 1:23 ` [PATCH] clk: shmobile: Add r8a7740, sh73a0 SoCs to MSTP bindings Simon Horman
2014-09-24 5:15 ` [GIT PULL] Second Round of Renesas ARM Based SoC Clk Updates for v3.18 Olof Johansson
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=cover.1410484748.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--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).