From: Simon Horman <horms+renesas@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.13
Date: Tue, 01 Oct 2013 02:38:36 +0000 [thread overview]
Message-ID: <cover.1380514316.git.horms+renesas@verge.net.au> (raw)
In-Reply-To: <cover.1375842392.git.horms+renesas@verge.net.au>
Hi Kevin, Olof and Arnd,
please consider these Renesas ARM based SoC defconfig updates for v3.13.
This pull request is based on v3.12-rc1.
As I discussed with Olof recently, we are making solid progress towards
multi-platform with common-clocks being the last major hurdle. I do expect
to be able to start booting some shmobile boards using multi-platform
within the next few release cycles. However, we are not there yet and in
the mean time I would like to keep the defconfigs in good shape.
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-defconfig-for-v3.13
for you to fetch changes up to 6bb2e347899b297eea26f2658eac8fdcd633fba5:
ARM: shmobile: Add koelsch defconfig (2013-09-20 17:46:15 -0700)
----------------------------------------------------------------
Renesas ARM based SoC defconfig updates for v3.13
* Add defconfig for koelsch board
* Enable sound in defconfig for bockw board
* Enable R-Car DU DRM in defconfig for lager and marzen boards
----------------------------------------------------------------
Kuninori Morimoto (1):
ARM: shmobile: bockw defconfig: add Sound support
Laurent Pinchart (2):
ARM: shmobile: marzen: Select DRM_RCAR_DU in defconfig
ARM: shmobile: lager: Select DRM_RCAR_DU in defconfig
Simon Horman (1):
ARM: shmobile: Add koelsch defconfig
arch/arm/configs/bockw_defconfig | 4 +++
arch/arm/configs/koelsch_defconfig | 54 ++++++++++++++++++++++++++++++++++++++
arch/arm/configs/lager_defconfig | 2 ++
arch/arm/configs/marzen_defconfig | 2 ++
4 files changed, 62 insertions(+)
create mode 100644 arch/arm/configs/koelsch_defconfig
next prev parent reply other threads:[~2013-10-01 2:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 4:23 [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.12 Simon Horman
2013-08-07 4:24 ` [GIT PULL 1/4] ARM: shmobile: marzen: Enable ARM_APPENDED_DTB in defconfig Simon Horman
2013-08-07 4:24 ` [GIT PULL 2/4] ARM: shmobile: Add lager defconfig Simon Horman
2013-08-07 4:24 ` [GIT PULL 3/4] ARM: shmobile: ape6evm: Enable gpio-keys in defconfig Simon Horman
2013-08-07 4:24 ` [GIT PULL 4/4] ARM: shmobile: ape6evm: Enable gpio-leds " Simon Horman
2013-08-14 8:04 ` [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.12 Olof Johansson
2013-08-18 3:57 ` Simon Horman
2013-10-01 2:38 ` Simon Horman [this message]
2013-10-01 2:38 ` [PATCH 1/4] ARM: shmobile: marzen: Select DRM_RCAR_DU in defconfig Simon Horman
2013-10-01 2:38 ` [PATCH 2/4] ARM: shmobile: lager: " Simon Horman
2013-10-01 2:38 ` [PATCH 3/4] ARM: shmobile: bockw defconfig: add Sound support Simon Horman
2013-10-01 2:38 ` [PATCH 4/4] ARM: shmobile: Add koelsch defconfig Simon Horman
2013-10-07 18:38 ` [GIT PULL 0/4] Renesas ARM based SoC defconfig updates for v3.13 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.1380514316.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).