linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Third Round of Renesas ARM Based SoC Fixes for v3.19
Date: Fri, 30 Jan 2015 09:45:16 +0900	[thread overview]
Message-ID: <cover.1422577690.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these third round of Renesas ARM based SoC fixes for v3.19.

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


This fixes a regression in the r8a7790 and r8a73a4 SoCs due to
9a1091ef0017c40a ("irqchip: gic: Support hierarchy irq domain.")
which was included in v3.19-rc1.

This pull-request is targeted at v3.19. r8a7790 patch in this pull-request
conflicts with the patch "ARM: shmobile: lager: Remove legacy board
support" which was included in the pull request "Renesas ARM Based SoC
Lager Board Removal for v3.20" which you have pulled for v3.20. The
conflict occurs because board-lager.c is removed in that patch whereas
this series updates that file.

In other words, this series fixes board code for the lager/r8a7790 for v3.19
which is scheduled for removal in v3.20.


The following changes since commit f469cde20a7ee342070b4a459b6fce469a3186db:

  ARM: shmobile: r8a7779: Instantiate GIC from C board code in legacy builds (2015-01-17 09:28:41 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc-fixes3-for-v3.19

for you to fetch changes up to 77cf5166f21c3b73b04571311dc89a327424f594:

  ARM: shmobile: r8a7790: Instantiate GIC from C board code in legacy builds (2015-01-29 17:52:38 +0900)

----------------------------------------------------------------
Third Round of Renesas ARM Based SoC Fixes for v3.19

* Instantiate GIC from C board code in legacy builds on r8a7790 and r8a73a4

----------------------------------------------------------------
Magnus Damm (2):
      ARM: shmobile: r8a73a4: Instantiate GIC from C board code in legacy builds
      ARM: shmobile: r8a7790: Instantiate GIC from C board code in legacy builds

 arch/arm/mach-shmobile/board-ape6evm.c   | 20 ++++++++++++++++++++
 arch/arm/mach-shmobile/board-lager.c     | 13 +++++++++++++
 arch/arm/mach-shmobile/setup-rcar-gen2.c |  2 ++
 arch/arm/mach-shmobile/timer.c           | 12 ++++++++++++
 4 files changed, 47 insertions(+)

             reply	other threads:[~2015-01-30  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  0:45 Simon Horman [this message]
2015-01-30  0:45 ` [PATCH 1/2] ARM: shmobile: r8a73a4: Instantiate GIC from C board code in legacy builds Simon Horman
2015-01-30  0:45 ` [PATCH 2/2] ARM: shmobile: r8a7790: " Simon Horman
2015-02-01  1:30 ` [GIT PULL] Third Round of Renesas ARM Based SoC Fixes for v3.19 Olof Johansson
2015-02-02  0:24   ` Simon Horman
2015-02-02  0:27     ` Olof Johansson
2015-02-02  1:53       ` 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.1422577690.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).