From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #2 (deadline November 17)
Date: Tue, 5 Nov 2013 00:07:28 +0100 [thread overview]
Message-ID: <20131105000728.49c0d1a6@skate> (raw)
In-Reply-To: <5278143A.5070505@mind.be>
Dear Arnout Vandecappelle,
On Mon, 04 Nov 2013 22:40:10 +0100, Arnout Vandecappelle wrote:
> I completely agree, that was the reason that I created the patch in
> the first place.
>
> Unfortunately, the x86_defconfig is _huge_. And as mentioned by
> ThomasP, the other architecture's defconfigs aren't worth much. So I
> don't think this patch is really valuable after all.
I agree. For anyone sane, x86_defconfig is basically unusable due to
the enormous number of options that it enables.
And for other architectures, a default defconfig doesn't make much
sense, since there usually isn't any "sane" default. I very much prefer
users to be asked loudly to provide a proper defconfig rather than
having Buildroot pick the kernel default one, and then have users
wonder why the kernel doesn't boot on their platform.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-04 23:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 15:09 [Buildroot] Patchwork oldest patches cleanup #2 (deadline November 17) Thomas De Schampheleire
2013-11-04 7:03 ` Arnout Vandecappelle
2013-11-04 8:30 ` Thomas De Schampheleire
2013-11-04 10:36 ` Arnout Vandecappelle
2013-11-04 11:17 ` Thomas De Schampheleire
2013-11-04 21:40 ` Arnout Vandecappelle
2013-11-04 23:07 ` Thomas Petazzoni [this message]
2013-11-05 8:06 ` Thomas De Schampheleire
2013-11-10 16:18 ` Thomas De Schampheleire
2013-11-11 13:50 ` Ryan Barnett
2013-11-15 9:47 ` Thomas De Schampheleire
2013-11-17 9:12 ` Thomas De Schampheleire
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=20131105000728.49c0d1a6@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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