All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm 2009-01-28-02-17 uploaded (i386 build errors: cpusets & kexec)
Date: Wed, 28 Jan 2009 08:56:31 -0800	[thread overview]
Message-ID: <49808E3F.1090805@oracle.com> (raw)
In-Reply-To: <200901281019.n0SAJ9C6013727@imap1.linux-foundation.org>

akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-01-28-02-17 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/
> 
> and will soon be available at
> 
>    git://git.zen-sources.org/zen/mmotm.git


10 randconfigs on i386, 1 good build.

The other 9 ended with either of these build errors:

init/main.c:876: error: 'struct task_struct' has no member named 'mems_allowed'
CONFIG_CPUSETS=n


or

kernel/printk.c:142: error: implicit declaration of function 'VMCOREINFO_SYMBOL'
# CONFIG_KEXEC is not set

-- 
~Randy

  reply	other threads:[~2009-01-28 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 10:19 mmotm 2009-01-28-02-17 uploaded akpm
2009-01-28 16:56 ` Randy Dunlap [this message]
2009-01-29  0:30   ` mmotm 2009-01-28-02-17 uploaded (i386 build errors: cpusets & kexec) Andrew Morton
2009-01-29  2:28     ` Simon Horman
2009-01-29 12:09       ` Neil Horman
2009-01-29 14:20         ` Vivek Goyal
2009-01-29 19:28           ` Neil Horman
2009-01-29 18:01         ` Andrew Morton
2009-01-29 19:27           ` Neil Horman
2009-01-29 19:48             ` Andrew Morton
2009-01-29 21:15               ` Neil Horman
2009-01-29  3:43 ` mmotm 2009-01-28-02-17 uploaded Valdis.Kletnieks
2009-01-29 17:44   ` Andrew Morton
2009-01-29  4:03 ` Valdis.Kletnieks
2009-01-29 16:25 ` mmotm 2009-01-28-02-17 uploaded - docking station issues Valdis.Kletnieks
2009-01-31  5:03   ` Andrew Morton
2009-01-31  5:03     ` Andrew Morton
2009-01-31  8:40     ` Valdis.Kletnieks
2009-01-31  8:52       ` Andrew Morton

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=49808E3F.1090805@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --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.