[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51C2173E.3080405@suse.cz>
Date: Wed, 19 Jun 2013 22:40:30 +0200
From: Michal Marek <mmarek@...e.cz>
To: "Yann E. MORIN" <yann.morin.1998@...e.fr>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [pull request] Pull request for branch yem-kconfig-for-next
Dne 19.6.2013 00:44, Yann E. MORIN napsal(a):
> From: "Yann E. MORIN" <yann.morin.1998@...e.fr>
>
> Hello Michal, All!
>
> These are the patches against kconfig that I have accumulated for 3.11,
> and for which I plan to later send a proper pull-request.
>
> Note-whorthy this time:
> - fix values of tristates that are selected by boolean choices (Arve)
> - fix choice randomisation in presence of KCONFIG_ALLCONFIG (me)
> - fix choice randomisation selecting more than one value in
> a choice (but only if it is conditional) (me)
> - fix choice-in-a-choice randomisation not selecting any value
> for the inner-most choice (me)
>
> Also, some code-cleanups and eye-candy:
> - mconf and nconf code cleanups (Dirk, Sedat)
> - mconf and nconf eye-candy (Dirk)
> - scripts/config script-name in help text (Clément)
> - heuristic to sort found symbols by relevance (me)
> - more randconfig debugging help (me)
>
> Note: this series is for review before I send an official pull-request.
> I want to avoid the debacle [0] [1] of the last kconfig breakage I caused
> with my previous kconfig "fix" to randomising choices in presence of
> KCONFIG_ALLCONFIG.
>
> I would like to send an official pull-request early next week, so all of
> these can land early in -next, so they get some real-life t4esting before
> the next merge windows open. So please, please, test this carefully. ;-)
I tested this a bit, it works fine. Unless somebody else finds issues,
I'll merge it.
Thanks,
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists