Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Randomization of kconfig choices?
Date: Tue, 18 Jun 2013 18:49:04 +0200	[thread overview]
Message-ID: <20130618164904.GB3952@free.fr> (raw)
In-Reply-To: <20130618093107.6c08e477@skate>

Thomas, All,

On 2013-06-18 09:31 +0200, Thomas Petazzoni spake thusly:
> I'm coming to the news regarding the randomization of kconfig choices?
> I know you've put a lot of efforts to try to fix this problem, but if I
> remember correctly so far the proposed solutions had some remaining
> issues.

No, I could not come up with a satisfiable solution so far. I've put it
a bit in a limbo, so I can start afresh from a new angle.

There have been some fixes in this area recently, but alas, none fixes
the randomisation of choices in presence of KCONFIG_ALLCONFIG.

But I was planning to work on this this week. Let's see where that will
get us...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2013-06-18 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18  7:31 [Buildroot] Randomization of kconfig choices? Thomas Petazzoni
2013-06-18 16:49 ` Yann E. MORIN [this message]
2013-06-18 17:00   ` Thomas Petazzoni
2013-06-18 17:15     ` Yann E. MORIN
2013-06-18 17:19       ` Thomas Petazzoni
2013-06-18 18:10       ` Yann E. MORIN
2013-06-19  6:28         ` Thomas Petazzoni

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=20130618164904.GB3952@free.fr \
    --to=yann.morin.1998@free.fr \
    --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