From: Simon Horman <horms+renesas@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC DT Clocksource Updates for v3.19
Date: Thu, 30 Oct 2014 01:50:49 +0000 [thread overview]
Message-ID: <cover.1414629281.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM based SoC DT clocksource updates for v3.19.
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt-clocksource-for-v3.19
for you to fetch changes up to d5153cd734dd6c1243bb3dc98065be99b10d049f:
clocksource: sh_mtu2: Drop incorrect SoC family name (2014-10-27 10:00:36 +0900)
----------------------------------------------------------------
Renesas ARM Based SoC DT Clocksource Updates for v3.19
* sh_mtu2: Drop incorrect SoC family name
* sh_tmu: Document r8a7778 and r8a7740 bindings
----------------------------------------------------------------
Geert Uytterhoeven (3):
clocksource: sh_tmu: Document R-Mobile r8a7740 binding
clocksource: sh_tmu: Document r8a7778 binding
clocksource: sh_mtu2: Drop incorrect SoC family name
Documentation/devicetree/bindings/timer/renesas,mtu2.txt | 2 +-
Documentation/devicetree/bindings/timer/renesas,tmu.txt | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2014-10-30 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 1:50 Simon Horman [this message]
2014-10-30 1:50 ` [PATCH 1/3] clocksource: sh_tmu: Document R-Mobile r8a7740 binding Simon Horman
2014-10-30 1:50 ` [PATCH 2/3] clocksource: sh_tmu: Document r8a7778 binding Simon Horman
2014-10-30 1:50 ` [PATCH 3/3] clocksource: sh_mtu2: Drop incorrect SoC family name Simon Horman
2014-11-04 22:46 ` [GIT PULL] Renesas ARM Based SoC DT Clocksource Updates for v3.19 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.1414629281.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).