From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Third Round of Renesas ARM Based Soc Updates for v3.19
Date: Thu, 13 Nov 2014 21:50:22 +0300 [thread overview]
Message-ID: <5464FD6E.1090404@cogentembedded.com> (raw)
In-Reply-To: <cover.1415841454.git.horms+renesas@verge.net.au>
Hello.
On 11/13/2014 04:20 AM, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> Please consider these third round of Renesas ARM based soc updates for v3.19.
> This pull request is based on the previous round of
> such requests, tagged as renesas-soc2-for-v3.19,
> which I have already sent a pull-request for.
> This pull request is based on the previous round of
> such requests, tagged as renesas-soc2-for-v3.19,
> which I have already sent a pull-request for.
OK, but we've got it the first time. :-)
> Please note that "ARM: shmobile: always build rcar setup for armv7"
> corrects a build failure in allmodconfig caused by "ARM: shmobile:
> rcar-gen2: Add CA7 arch_timer initialization for r8a7794" which
> is included in the first round of Renesas ARM Based SoC Soc Updates for
> v3.19, tagged as renesas-soc2-for-v3.19, which I have previously sent
> a pull-request for.
This is a third time you're repeating that. :-)
> To be clear, this pull request is based on renesas-soc2-for-v3.19 which
> is in turn based on renesas-soc2-for-v3.19.
Based on itself? :-)
> The following changes since commit 950a3f0e7dd32c372c9957d5c050b08de7ec9e56:
> ARM: shmobile: Enable PCI domains for R-Car Gen2 devices (2014-11-05 14:50:17 +0900)
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc3-for-v3.19
> for you to fetch changes up to e3d163329753b3b473f40c9be71561ed8eb98aea:
> ARM: shmobile: always build rcar setup for armv7 (2014-11-12 18:14:42 +0900)
> ----------------------------------------------------------------
> Third Round of Renesas ARM Based Soc Updates for v3.19
> * Always build rcar setup for armv7
> - Fixes allmodconfig build fauilre caused by
Failure.
> "ARM: shmobile: always build rcar setup for armv7"
Caused by itself? :-)
> * Add restart callback to sh73a0
> ----------------------------------------------------------------
> Arnd Bergmann (1):
> ARM: shmobile: always build rcar setup for armv7
> Geert Uytterhoeven (1):
> ARM: shmobile: sh73a0: Add restart callback
> arch/arm/mach-shmobile/Makefile | 1 +
> arch/arm/mach-shmobile/setup-sh73a0.c | 8 ++++++++
> 2 files changed, 9 insertions(+)
WBR, Sergei
next prev parent reply other threads:[~2014-11-13 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 1:20 [GIT PULL] Third Round of Renesas ARM Based Soc Updates for v3.19 Simon Horman
2014-11-13 1:20 ` [PATCH 1/2] ARM: shmobile: sh73a0: Add restart callback Simon Horman
2014-11-13 1:20 ` [PATCH 2/2] ARM: shmobile: always build rcar setup for armv7 Simon Horman
2014-11-13 18:50 ` Sergei Shtylyov [this message]
2014-11-14 0:32 ` [GIT PULL] Third Round of Renesas ARM Based Soc Updates for v3.19 Simon Horman
2014-11-19 21:16 ` Arnd Bergmann
2014-11-20 0:42 ` Simon Horman
2014-11-20 7:56 ` Geert Uytterhoeven
2014-11-20 9:04 ` Arnd Bergmann
2014-11-20 9:19 ` Geert Uytterhoeven
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=5464FD6E.1090404@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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).