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 Soc Updates for v3.18
Date: Fri, 19 Sep 2014 04:14:19 +0000	[thread overview]
Message-ID: <cover.1411100007.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 soc updates for v3.18.

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


The following changes since commit 1370078db37de2aa5e906ae2b5dbbb6ba289adb4:

  ARM: shmobile: r8a7794: Remove unnecessary #ifdef CONFIG_USE_OF (2014-09-11 09:51:16 +0900)

are available in the git repository at:

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

for you to fetch changes up to 8237f9e5c38098aeb8570a77bacd0fe0ebc61dfa:

  ARM: shmobile: r8a7740 legacy: Fix copied bug in comment (2014-09-17 09:20:53 +0900)

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

* r8a7740: Fix documentation error coppied from elsewhere
* r8a7794: Reserve memory for CMA in a manner consistent to
           other R-Car Gen2 SoCs

----------------------------------------------------------------
Geert Uytterhoeven (1):
      ARM: shmobile: r8a7740 legacy: Fix copied bug in comment

Magnus Damm (1):
      ARM: shmobile: r8a7794: Reserve memory as other R-Car Gen2 SoCs

 arch/arm/mach-shmobile/pm-r8a7740.c    | 2 +-
 arch/arm/mach-shmobile/setup-r8a7794.c | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

  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 ` [GIT PULL] Fifth Round of Renesas ARM Based SoC DT Updates for v3.18 Simon Horman
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 ` Simon Horman [this message]
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.1411100007.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).