From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>, Jack Steiner <steiner@sgi.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: mmotm 2010-05-11-18-20 uploaded (aio build; add numa)
Date: Wed, 12 May 2010 12:42:44 -0700 [thread overview]
Message-ID: <20100512124244.20365b3c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <x49bpclrqtt.fsf@segfault.boston.devel.redhat.com>
On Wed, 12 May 2010 13:07:58 -0400 Jeff Moyer wrote:
> Randy Dunlap <randy.dunlap@oracle.com> writes:
>
> > On Tue, 11 May 2010 18:21:22 -0700 akpm@linux-foundation.org wrote:
> >
> >> The mm-of-the-moment snapshot 2010-05-11-18-20 has been uploaded to
> >>
> >> http://userweb.kernel.org/~akpm/mmotm/
> >>
> >> and will soon be available at
> >>
> >> git://zen-kernel.org/kernel/mmotm.git
> >
> >
> > aio-fix-the-compat-vectored-operations.patch:
> >
> > (1) when CONFIG_AIO is not enabled, there are hundreds of this warning:
> >
> > include/linux/aio.h:226: warning: no return statement in function returning non-void
> >
> >
> > (2) when CONFIG_AIO=y, CONFIG_IA32_EMULATION=n, CONFIG_COMPAT=n:
> >
> > fs/aio.c:1393: error: implicit declaration of function 'compat_rw_copy_check_uvector'
>
> Sorry about that. I'll fix it up, but probably can't get to it until
> Monday. Hopefully that's an ok timeframe.
Andrew's patch works_for_me. (Ack)
During the build, I got another (unrelated) build error:
kernel/built-in.o: In function `copy_process':
fork.c:(.text+0x162b6): undefined reference to `__node_random'
fork.c:(.text+0x162cd): undefined reference to `__node_random'
kernel/fork.c needs to #include <linux/nodemask.h>
[builds...]
But that is not enough. The config file has CONFIG_CPUSETS=y
and CONFIG_NUMA=n, so __node_random() is not being built at all.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-12 19:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 1:21 mmotm 2010-05-11-18-20 uploaded akpm
2010-05-12 16:50 ` mmotm 2010-05-11-18-20 uploaded (aio build) Randy Dunlap
2010-05-12 17:07 ` Jeff Moyer
2010-05-12 17:09 ` Randy Dunlap
2010-05-12 19:42 ` Randy Dunlap [this message]
2010-05-12 19:52 ` mmotm 2010-05-11 - dies in pm_qos_update_request() Valdis.Kletnieks
2010-05-12 21:07 ` Rafael J. Wysocki
2010-05-12 22:12 ` Valdis.Kletnieks
2010-05-12 22:33 ` Rafael J. Wysocki
2010-05-13 14:34 ` Valdis.Kletnieks
2010-05-13 22:24 ` Rafael J. Wysocki
2010-05-14 23:43 ` mark gross
2010-05-13 22:32 ` Rafael J. Wysocki
2010-05-12 20:39 ` [PATCH -mmotm] misc: fix ad525X_dpot build Randy Dunlap
2010-05-12 20:53 ` Hennerich, Michael
2010-05-12 20:39 ` [PATCH -mmotm] backlight: fix adp8860_bl build errors Randy Dunlap
2010-05-12 20:54 ` Hennerich, Michael
2010-05-13 15:06 ` mmotm 2010-05-11-18-20 uploaded Valdis.Kletnieks
2010-05-13 16:02 ` Dmitry Torokhov
2010-05-13 16:20 ` Mauro Carvalho Chehab
2010-05-13 16:29 ` Valdis.Kletnieks
2010-05-13 17:32 ` Mauro Carvalho Chehab
2010-05-19 23:34 ` Mauro Carvalho Chehab
2010-05-20 4:57 ` Mauro Carvalho Chehab
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=20100512124244.20365b3c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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;
as well as URLs for NNTP newsgroup(s).