public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Peter Korsgaard <jacmet@sunsite.dk>,
	linux-kbuild@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: [PATCH] kconfig: make randconfig fair for booleans
Date: Mon, 26 Jul 2010 08:20:16 -0700	[thread overview]
Message-ID: <4C4DA7B0.8010401@oracle.com> (raw)
In-Reply-To: <4C4D9308.3040108@suse.cz>

On 07/26/10 06:52, Michal Marek wrote:
> On 26.7.2010 11:59, Michal Marek wrote:
>> On 23.7.2010 23:11, Sam Ravnborg wrote:
>>> On Thu, Jul 22, 2010 at 02:24:57PM +0200, Peter Korsgaard wrote:
>>>> Give boolean symbols a 50% chance of getting enabled, rather than 67%.
>>>>
>>>> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
>>>
>>> Good catch!
>>>
>>> Acked-by: Sam Ravnborg <sam@ravnborg.org>
>>>
>>> Michal - I assume you apply this for next merge window.
>>
>> Yes, will do. I've been busy (again :)) for the last two weeks, so only
>> reviewed the few patches for .35.
> 
> Applied now.
> 
> CCing Randy. FYI, you'll see a little less builds with CONFIG_MODULES=y
> starting with tomorrow's linux-next. It should not matter unless you're
> maintaining some statistics.

Thanks.  Not a problem.  No stats.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2010-07-26 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 12:24 [PATCH] kconfig: make randconfig fair for booleans Peter Korsgaard
2010-07-23 21:11 ` Sam Ravnborg
2010-07-26  9:59   ` Michal Marek
2010-07-26 13:52     ` Michal Marek
2010-07-26 15:20       ` Randy Dunlap [this message]

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=4C4DA7B0.8010401@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jacmet@sunsite.dk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /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