From: Andrew Morton <akpm@linux-foundation.org>
To: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>
Cc: "Wu, Fengguang" <fengguang.wu@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [next:master 4658/4676] undefined reference to `copy_user_page'
Date: Thu, 5 Feb 2015 12:21:15 -0800 [thread overview]
Message-ID: <20150205122115.8fe1037870b76d75afc3fb03@linux-foundation.org> (raw)
In-Reply-To: <100D68C7BA14664A8938383216E40DE040853FB4@FMSMSX114.amr.corp.intel.com>
On Thu, 22 Jan 2015 15:12:15 +0000 "Wilcox, Matthew R" <matthew.r.wilcox@intel.com> wrote:
> Looks like mips *declares* copy_user_page(), but never *defines* an implementation.
>
> It's documented in Documentation/cachetlb.txt, but it's not (currently) called if the architecture defines its own copy_user_highpage(), so some bitrot has occurred. ARM is currently fixing this, and MIPS will need to do the same.
>
> (We can't use copy_user_highpage() in DAX because we don't necessarily have a struct page for 'from'.)
Has there been any progress on this? It would be unpleasant to merge
DAX into 3.19 and break MIPS and ARM.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-02-05 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 5:40 kbuild test robot
2015-01-22 15:12 ` Wilcox, Matthew R
2015-02-05 20:21 ` Andrew Morton [this message]
2015-02-05 20:22 ` Wilcox, Matthew R
2015-02-05 20:25 ` Andrew Morton
2015-02-05 20:45 ` Wilcox, Matthew R
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=20150205122115.8fe1037870b76d75afc3fb03@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.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