linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Fifth Round of Renesas ARM Based SoC DT Updates for v3.18
Date: Fri, 19 Sep 2014 04:14:13 +0000	[thread overview]
Message-ID: <cover.1411099817.git.horms+renesas@verge.net.au> (raw)
In-Reply-To: <cover.1380874512.git.horms+renesas@verge.net.au>

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these fifth round of Renesas ARM based SoC DT updates for v3.18.

This pull request is based on the previous round of
such requests, tagged as renesas-dt4-for-v3.18,
which I have already sent a pull-request for.


The following changes since commit a742795be9ceae2853ca71f216193f29da151da8:

  ARM: shmobile: Initial Alt board device tree (2014-09-09 11:29:27 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt5-for-v3.18

for you to fetch changes up to 08adafd4a1f8c9b6e2c49d955a0e45743c9ffd9a:

  ARM: shmobile: Add manufacturer for KZM boards (2014-09-17 09:23:14 +0900)

----------------------------------------------------------------
Fifth Round of Renesas ARM Based SoC DT Updates for v3.18

* Document manufacturer for KZM boards
* Use SoC-specific irqc compatible property

----------------------------------------------------------------
Geert Uytterhoeven (2):
      ARM: shmobile: r8a73a4 dtsi: Add SoC-specific irqc compatible property
      ARM: shmobile: Add manufacturer for KZM boards

 Documentation/devicetree/bindings/arm/shmobile.txt | 6 +++---
 arch/arm/boot/dts/r8a73a4.dtsi                     | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

  parent reply	other threads:[~2014-09-19  4:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04  8:19 [GIT PULL] Fifth Round of Renesas ARM based SoC fixes for v3.12 Simon Horman
2013-10-04  8:20 ` [PATCH] ARM: shmobile: ape6evm: fix incorrect placement of __initdata tag Simon Horman
2013-10-07 17:49 ` [GIT PULL] Fifth Round of Renesas ARM based SoC fixes for v3.12 Olof Johansson
2013-10-08  1:05   ` Simon Horman
2014-04-14  4:02 ` [GIT PULL] Fifth Round of Renesas ARM Based SoC DT Updates for v3.15 Simon Horman
2014-04-14  4:02   ` [PATCH] ARM: shmobile: lager: correct renesas,gpios to renesas,groups in sd[02] pfc Simon Horman
2014-09-19  4:14 ` Simon Horman [this message]
2014-09-19  4:14   ` [PATCH 1/2] ARM: shmobile: r8a73a4 dtsi: Add SoC-specific irqc compatible property Simon Horman
2014-09-19  4:14   ` [PATCH 2/2] ARM: shmobile: Add manufacturer for KZM boards Simon Horman
2014-09-25 16:09   ` [GIT PULL] Fifth Round of Renesas ARM Based SoC DT Updates for v3.18 Arnd Bergmann
2014-09-19  4:14 ` [GIT PULL] Fifth Round of Renesas ARM Based SoC Soc " Simon Horman
2014-09-19  4:14   ` [PATCH 1/2] ARM: shmobile: r8a7794: Reserve memory as other R-Car Gen2 SoCs Simon Horman
2014-09-19  4:14   ` [PATCH 2/2] ARM: shmobile: r8a7740 legacy: Fix copied bug in comment Simon Horman
2014-09-25 16:11   ` [GIT PULL] Fifth Round of Renesas ARM Based SoC Soc Updates for v3.18 Arnd Bergmann

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.1411099817.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).