From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options
Date: Wed, 31 Dec 2014 15:17:34 +0100 [thread overview]
Message-ID: <20141231151734.0c95b119@free-electrons.com> (raw)
In-Reply-To: <20141030230310.4b91e6ab@free-electrons.com>
Hello,
On Thu, 30 Oct 2014 23:03:10 +0100, Thomas Petazzoni wrote:
> I was going to apply this, and then I tested it, to discover that it
> then causes the same problem as the one we have with randpackageconfig
> today: none of the choice options get randomized anymore. So before
> this patch, if you do "randconfig", you get proper randomization. After
> this patch, if you do "randconfig", it only generates i386
> configurations.
>
> I admit it's not really an issue introduced by the patch as the issue
> already exists for randpackageconfig. But it's very annoying :/
Any comment about this?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-31 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:24 [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options Arnout Vandecappelle
2014-10-14 9:24 ` [Buildroot] [PATCH v3 2/2] randconfig: seed with BR2_RAND_PRESEED_CONFIG_FILES Arnout Vandecappelle
2014-10-19 9:00 ` Yann E. MORIN
2014-10-30 22:03 ` [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options Thomas Petazzoni
2014-12-31 14:17 ` Thomas Petazzoni [this message]
2015-01-08 20:36 ` Arnout Vandecappelle
2015-01-08 20:43 ` Thomas Petazzoni
2015-01-24 23:00 ` Arnout Vandecappelle
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=20141231151734.0c95b119@free-electrons.com \
--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