From: Michael Ellerman <michael@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
Daniel Walker <dwalker@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [GIT PULL] ARM MSM updates for 2.6.35-rc1
Date: Thu, 03 Jun 2010 13:44:58 +1000 [thread overview]
Message-ID: <1275536698.22020.81.camel@concordia> (raw)
In-Reply-To: <alpine.LFD.2.00.1006021803350.8175@i5.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Wed, 2010-06-02 at 18:20 -0700, Linus Torvalds wrote:
>
> Now, I'm actually considering just getting rid of all the 'defconfig'
> files entirely. The x86 model is sane (there's two of them, nobody likely
> uses them), but ARM and POWERPC (and to a lesser config SH and MIPS) have
> turned the whole concept into a disgusting mess.
I agree that the defconfig mechanism is broken (ie. carrying the full
text in tree), but the concept is sane IMHO.
What'd be nice is if the defconfig could just be a delta against a base
config for the architecture - that would make most of them reasonably
small, just turning on/off a few options.
You can sort of do that today, by just storing a delta, but oldconfig
will silently turn off things you have enabled if prereqs change, so
that doesn't really work I think.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-03 3:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 21:52 [GIT PULL] ARM MSM updates for 2.6.35-rc1 Daniel Walker
2010-06-02 20:50 ` Daniel Walker
2010-06-02 21:27 ` Linus Torvalds
2010-06-02 21:39 ` Linus Torvalds
2010-06-02 21:56 ` Daniel Walker
2010-06-02 22:30 ` Daniel Walker
2010-06-02 23:27 ` Kevin Hilman
2010-06-03 1:20 ` Linus Torvalds
2010-06-03 3:44 ` Michael Ellerman [this message]
2010-06-03 4:26 ` Linus Torvalds
2010-06-03 16:11 ` Tony Lindgren
2010-06-04 5:34 ` Eric Miao
2010-06-03 4:45 ` Ben Dooks
2010-06-03 5:36 ` Ben Dooks
2010-06-04 8:27 ` Vincent Sanders
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=1275536698.22020.81.camel@concordia \
--to=michael@ellerman.id.au \
--cc=dwalker@codeaurora.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).