From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Fixes for v3.14
Date: Fri, 10 Jan 2014 11:45:34 +0900 [thread overview]
Message-ID: <cover.1389321620.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
please consider these renesas ARM Based SoC Fixes for v3.14.
This pull-request is based on the Third Round of Renesas ARM Based SoC
Updates for v3.14, tagged as renesas-soc3-for-v3.14, which you have
previously pulled.
It resolves a problem introduced by a patch included in the second round of such
changes, tagged as renesas-soc2-for-v3.14, which you have also previously
pulled.
renesas-soc3-for-v3.14 is based on renesas-soc2-for-v3.14.
The following changes since commit d85bcfa916ffdf078f188aeab60f738b290f4309:
arm: shmobile: r7s72100: add i2c clocks (2013-12-24 21:09:19 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc-fixes-for-v3.14
for you to fetch changes up to db455c786886465c4d7fcd012fe2684b4c887776:
ARM: shmobile: r8a7790: Fix I2C controller names (2014-01-06 14:25:39 +0900)
----------------------------------------------------------------
Renesas ARM Based SoC Fixes for v3.14
* r8a7790 (R-Car H2) SoC
- Correct I2C controller names
This fixes the issue introduced by
b448c904f5058b6c "ARM: shmobile: r8a7790: add I2C support"
which is queued-up for v3.14.
----------------------------------------------------------------
Valentine Barshak (1):
ARM: shmobile: r8a7790: Fix I2C controller names
arch/arm/mach-shmobile/clock-r8a7790.c | 8 ++++----
arch/arm/mach-shmobile/setup-r8a7790.c | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2014-01-10 2:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 2:45 Simon Horman [this message]
2014-01-10 2:46 ` [PATCH] ARM: shmobile: r8a7790: Fix I2C controller names Simon Horman
2014-01-14 18:44 ` [GIT PULL] Renesas ARM Based SoC Fixes for v3.14 Kevin Hilman
2014-01-15 0:04 ` Simon Horman
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.1389321620.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).