From: Mark Salter <msalter@redhat.com>
To: Mel Gorman <mgorman@suse.de>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: linux-next link failure
Date: Mon, 23 Jul 2012 14:16:49 -0400 [thread overview]
Message-ID: <1343067410.3672.8.camel@deneb.redhat.com> (raw)
Today's linux-next has a link failure on no-mmu systems:
fs/built-in.o: In function `nfs_file_direct_read':
(.text+0x80968): undefined reference to `get_kernel_page'
fs/built-in.o: In function `nfs_file_direct_write':
(.text+0x81178): undefined reference to `get_kernel_page'
The problem is that get_kernel_page does not exist if CONFIG_MMU is not
defined. This is the patch that added get_kernel_page():
mm: add get_kernel_page[s] for pinning of kernel addresses for I/O
and the reference to get_kernelpage was added with:
nfs: enable swap on NFS
--Mark
next reply other threads:[~2012-07-23 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 18:16 Mark Salter [this message]
2012-07-24 10:18 ` linux-next link failure Mel Gorman
2012-07-24 10:27 ` Mel Gorman
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=1343067410.3672.8.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=mgorman@suse.de \
/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).