All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [next:akpm 147/308] ERROR: "get_kernel_page" [fs/nfs/nfs.ko] undefined!
Date: Tue, 31 Jul 2012 13:53:45 +0000	[thread overview]
Message-ID: <20120731135345.GQ612@suse.de> (raw)
In-Reply-To: <20120731114516.GA17252@localhost>

On Tue, Jul 31, 2012 at 07:45:16PM +0800, Fengguang Wu wrote:
> Hi Mel,
> 
> Kernel build failed on
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm
> head:   6e81859e67505899e9d6c4f5b1cd9fbcf65997bd
> commit: 2866c9bbc69e80d22caef0230ebc3d95df501b68 [147/308] nfs: enable swap on NFS
> config: blackfin-BF533-EZKIT_defconfig (attached as .config)
> 
> All related error/warning messages:
> 
> ERROR: "get_kernel_page" [fs/nfs/nfs.ko] undefined!
> 

This is a no MMU config. There should be a patch in-flight in Andrew's tree
called mm-add-get_kernel_page-for-pinning-of-kernel-addresses-for-i-o-fix
that fixes this by moving the missing functions from memory.c to swap.c

-- 
Mel Gorman
SUSE Labs

      reply	other threads:[~2012-07-31 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 11:45 [next:akpm 147/308] ERROR: "get_kernel_page" [fs/nfs/nfs.ko] undefined! Fengguang Wu
2012-07-31 13:53 ` Mel Gorman [this message]

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=20120731135345.GQ612@suse.de \
    --to=mgorman@suse.de \
    --cc=kernel-janitors@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.