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 Defconfig Updates for v3.18
Date: Tue, 2 Sep 2014 10:31:52 +0900 [thread overview]
Message-ID: <cover.1409621323.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these third round of Renesas ARM based SoC defconfig
updates for v3.18.
This pull request is based on the previous round of
such requests, tagged as renesas-defconfig2-for-v3.18,
which I have already sent a pull-request for.
The following changes since commit 99923753e7c17a9c9d46bfe4d7fa543e426ec647:
ARM: shmobile: bockw: Do not disable SUSPEND in defconfig (2014-08-22 10:40:31 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-defconfig3-for-v3.18
for you to fetch changes up to de46e95cdb8671e2b0728923b8113654779c3ba8:
ARM: shmobile: Enable Armadillo 800 EVA board in multiplatform defconfig (2014-09-01 10:46:57 +0900)
----------------------------------------------------------------
Third Round of Renesas ARM Based SoC Defconfig Updates for v3.18
* Enable Armadillo 800 EVA board in multiplatform defconfig
----------------------------------------------------------------
Geert Uytterhoeven (1):
ARM: shmobile: Enable Armadillo 800 EVA board in multiplatform defconfig
arch/arm/configs/shmobile_defconfig | 12 ++++++++++++
1 file changed, 12 insertions(+)
next reply other threads:[~2014-09-02 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 1:31 Simon Horman [this message]
2014-09-02 1:31 ` [PATCH] ARM: shmobile: Enable Armadillo 800 EVA board in multiplatform defconfig Simon Horman
2014-09-05 16:02 ` [GIT PULL] Third Round of Renesas ARM Based SoC Defconfig 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.1409621323.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).