From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] Renesas ARM-based SoC defconfig for v3.8
Date: Wed, 17 Oct 2012 13:42:29 +0000 [thread overview]
Message-ID: <201210171342.29635.arnd@arndb.de> (raw)
In-Reply-To: <1350448698-26985-1-git-send-email-horms@verge.net.au>
On Wednesday 17 October 2012, Simon Horman wrote:
> Hi Olof, Hi Arnd,
>
> please consider the following defconfig enhancements for 3.8.
These look good to me, but I wonder what happened to the plan to reduce
the number of defconfig files we discussed before. Since you can build
a combined kernel that runs on all (or most) of the supported boards,
can you add a combined shmobile_defconfig that is able to work on
a wide variety of hardware and drop some of the less common defconfig
files?
Most of the modern platforms nowadays have just one defconfig that
covers everything.
Arnd
next prev parent reply other threads:[~2012-10-17 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 4:38 [GIT PULL] Renesas ARM-based SoC defconfig for v3.8 Simon Horman
2012-10-17 4:38 ` [PATCH 1/2] ARM: shmobile: mackerel: defconfig update Simon Horman
2012-10-17 4:38 ` [PATCH 2/2] ARM: shmobile: armadillo800eva: enable L2X0 cache on defconfig Simon Horman
2012-10-17 13:42 ` Arnd Bergmann [this message]
2012-10-18 0:58 ` [GIT PULL] Renesas ARM-based SoC defconfig for v3.8 Simon Horman
2012-10-18 7:29 ` Arnd Bergmann
2012-10-18 8:13 ` Simon Horman
2012-10-19 3:09 ` Simon Horman
2012-10-19 8:18 ` Arnd Bergmann
2012-10-22 0:33 ` Simon Horman
2012-10-22 1:51 ` Simon Horman
2012-10-22 14:12 ` Arnd Bergmann
2012-10-22 18:20 ` Nicolas Pitre
2012-10-30 7:45 ` Simon Horman
2012-10-30 21:41 ` Arnd Bergmann
2012-11-01 0:46 ` 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=201210171342.29635.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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