From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC sh73a0 Multiplatform Updates for v3.20
Date: Tue, 20 Jan 2015 10:27:32 +0900 [thread overview]
Message-ID: <cover.1421716945.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these second round of Renesas ARM based SoC sh73a0 multiplatform updates for v3.20.
This pull request is based on the previous round of
such requests, tagged as renesas-sh73a0-multiplatform-for-v3.20,
which I have already sent a pull-request for.
My understanding from Geert Uytterhoeven is that the above dependency
is required to avoid a lock-up.
The following changes since commit 93c9f0228a3d0a14640f86b3e8aeaf3c9b449bb7:
ARM: shmobile: kzm9g-reference: Remove board C code and DT file (2015-01-14 09:46:48 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-sh73a0-multiplatform2-for-v3.20
for you to fetch changes up to e42c8385cfec0579a103b365d61748f199bfe239:
ARM: shmobile: sh73a0 dtsi: Add Cortex-A9 TWD node (2015-01-17 09:36:35 +0900)
----------------------------------------------------------------
Second Round of Renesas ARM Based SoC sh73a0 Multiplatform Updates for v3.20
* Add Cortex-A9 TWD node
----------------------------------------------------------------
Geert Uytterhoeven (1):
ARM: shmobile: sh73a0 dtsi: Add Cortex-A9 TWD node
arch/arm/boot/dts/sh73a0.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
next reply other threads:[~2015-01-20 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 1:27 Simon Horman [this message]
2015-01-20 1:27 ` [PATCH] ARM: shmobile: sh73a0 dtsi: Add Cortex-A9 TWD node Simon Horman
2015-01-22 1:03 ` [GIT PULL] Second Round of Renesas ARM Based SoC sh73a0 Multiplatform Updates for v3.20 Simon Horman
2015-01-22 1:34 ` Olof Johansson
2015-01-22 2:01 ` Simon Horman
2015-01-22 6:36 ` Olof Johansson
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.1421716945.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).