Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #2 (deadline November 17)
Date: Mon, 04 Nov 2013 22:40:10 +0100	[thread overview]
Message-ID: <5278143A.5070505@mind.be> (raw)
In-Reply-To: <CAAXf6LXQ_1pYTCyr2nLwDa1J7kJUsSZCcbs03gr3OFaDPmX6gw@mail.gmail.com>

On 04/11/13 12:17, Thomas De Schampheleire wrote:
> Hi Arnout,
>
> On Mon, Nov 4, 2013 at 8:03 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
>> On 01/11/13 16:09, Thomas De Schampheleire wrote:
>> [snip]
>>
>>> linux: add default defconfig
>>> Arnout Vandecappelle <arnout@mind.be>
>>> http://patchwork.ozlabs.org/patch/181185
>>
>>
>>   This one didn't receive positive feedback, so I guess it's rejected. Short
>> recap: it allows you to build the kernel with the architecture's default
>> defconfig, which is typically a bloaty configuration that supports many
>> boards (if an appropriate device tree is present). IIRC the feedback was
>> that this wasn't usually appropriate for buildroot use cases.
>
> One annoyance I have is that if you want to quickly test something
> (for example when reviewing patches) and you enable a Linux kernel,
> you also have to specify a defconfig. Your patch would fix that use
> case. In such a test case, I typically don't care what is included in
> the kernel, because I would only compile-test.

  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.

  Regards,
  Arnout

> But I can also follow ThomasP's comments on that patch.
> There was a suggestion in case of x86 though, which in many cases
> would be ok for me in the above scenario. I wouldn't be against having
> just that...
>
> Best regards,
> Thomas
>
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-11-04 21:40 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 [this message]
2013-11-04 23:07       ` Thomas Petazzoni
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=5278143A.5070505@mind.be \
    --to=arnout@mind.be \
    --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