From: Randy Dunlap <randy.dunlap@oracle.com>
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: 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 12:41:26 -0800 [thread overview]
Message-ID: <49821476.7060500@oracle.com> (raw)
In-Reply-To: <200901291058.50466.inaky@linux.intel.com>
Inaky Perez-Gonzalez wrote:
> On Thursday 29 January 2009, Randy Dunlap wrote:
>> akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2009-01-29-02-29 has been uploaded to
>>>
>>> http://userweb.kernel.org/~akpm/mmotm/
>>>
>>> and will soon be available at
>>>
>>> git://git.zen-sources.org/zen/mmotm.git
>> Build fails with:
>>
>> ERROR: "d_level_wimax" [net/wimax/wimax.ko] undefined!
>> ERROR: "d_level_size_wimax" [net/wimax/wimax.ko] undefined!
>
> On it, Toralf Foerster just reported it.
>
> I got the fix, I am now verifying it.
>
> How do you guys generate all this configs? I thought I had tried all
> possible combinations and I guess I was wrong...
I just have a 'make randconfig' machine (repeat, repeat, ...).
--
~Randy
next prev parent reply other threads:[~2009-01-29 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 10:30 mmotm 2009-01-29-02-29 uploaded akpm
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
2009-01-29 20:41 ` Randy Dunlap [this message]
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=49821476.7060500@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.