On Tue, Jun 25, 2013 at 10:01 AM, Yann E. MORIN <yann.morin.1998@xxxxxxx> wrote: > Michal, All, > > On Monday 24 June 2013 20:11:59 Yann E. MORIN wrote: >> Currently, randconfig does randomise choice entries, unless KCONFIG_ALLCONFIG >> is specified. > [--SNIP--] >> This patch defers setting that a choice has a value until a symbol for >> that choice is indeed set, so that choices are properly randomised when >> KCONFIG_ALLCONFIG is set, but not if a symbol for that choice is set. > > I've just been informed by Fengguang that this patch breaks yet another > use-case of his, but this time KCONFIG_ALLCONFIG is not involved. > > I'll investigate this issue when I'm back home tonight (ie. ~16:00 UTC). > Sorry for the breakage (again...). :-( > > We really need a known, shared test-suite for kconfig... :-/ > [ CC Alexander ] A-propos, "testing Kconfig" I recommended to take into account the script of Alexander. In PM we discussed on where to place such scripts and that Alexander's patch needs some refreshing in your eyes. Maybe, Alexander can/will help as he is the original author. As said, this script helped in the Freetz router project to eliminate dozens of (logically) wrong Kconfig settings. IMHO there exist a lot of more, as there are "double/triple" checks in the Freetz-buildsystem, but hey noone is perfect :-). - Sedat - [1] http://freetz.org/browser/trunk/tools/developer/create-kconfig-warnings > Regards, > Yann E. MORIN. > > -- > .-----------------.--------------------.------------------.--------------------. > | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | > | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ | > | --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no | > | http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. | > '------------------------------'-------'------------------'--------------------' -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
