From: Valdis.Kletnieks@vt.edu
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm 2009-01-29-02-29 uploaded (wimax)
Date: Thu, 29 Jan 2009 14:23:54 -0500 [thread overview]
Message-ID: <49521.1233257034@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 29 Jan 2009 10:58:49 PST." <200901291058.50466.inaky@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
On Thu, 29 Jan 2009 10:58:49 PST, Inaky Perez-Gonzalez said:
> How do you guys generate all this configs? I thought I had tried all
> possible combinations and I guess I was wrong...
I think Randy has a special evilly-biased random generator for 'make randconfig'.
I just attract bad karma trying to build it on my laptop with the same config
I've used all along. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-01-29 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901291030.n0TAUhRI003046@imap1.linux-foundation.org>
2009-01-29 17:33 ` [PATCH -next/mmotm/resend] kmemtrace: fix printk formats Randy Dunlap
2009-01-29 18:51 ` Ingo Molnar
2009-01-29 21:35 ` Geert Uytterhoeven
2009-01-29 21:49 ` Randy Dunlap
2009-01-30 7:46 ` Eduard - Gabriel Munteanu
2009-01-30 15:12 ` Ingo Molnar
2009-01-29 17:49 ` mmotm 2009-01-29-02-29 uploaded (wimax) Randy Dunlap
2009-01-29 18:58 ` Inaky Perez-Gonzalez
2009-01-29 19:23 ` Valdis.Kletnieks [this message]
2009-01-29 20:41 ` Randy Dunlap
2009-01-29 21:46 ` [GIT PATCH] " Inaky Perez-Gonzalez
2009-01-29 21:59 ` [PATCH] wimax: fix build issue when debugfs is disabled Inaky Perez-Gonzalez
2009-01-29 22:08 ` Randy Dunlap
2009-01-30 1:19 ` David Miller
2009-01-30 3:41 ` Inaky Perez-Gonzalez
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=49521.1233257034@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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
all inboxes | Powered by JetHome®