From: kbuild test robot <fengguang.wu@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: drivers/nvdimm/pmem.c:367:3: error: implicit declaration of function '__phys_to_pfn'
Date: Sun, 6 Mar 2016 21:05:23 +0800 [thread overview]
Message-ID: <201603062121.s1ZUEjOS%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Hi Dan,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 67944024c1cdd897e49a09b0d6af3ea38d1388ca
commit: d2c0f041e1bb1260629ecea2161adb9778945aa3 libnvdimm, pfn, pmem: allocate memmap array in persistent memory
date: 7 weeks ago
config: ia64-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout d2c0f041e1bb1260629ecea2161adb9778945aa3
# save the attached .config to linux build tree
make.cross ARCH=ia64
All errors (new ones prefixed by >>):
drivers/nvdimm/pmem.c: In function 'nvdimm_namespace_attach_pfn':
>> drivers/nvdimm/pmem.c:367:3: error: implicit declaration of function '__phys_to_pfn' [-Werror=implicit-function-declaration]
.base_pfn = __phys_to_pfn(nsio->res.start),
^
cc1: some warnings being treated as errors
vim +/__phys_to_pfn +367 drivers/nvdimm/pmem.c
361 struct vmem_altmap *altmap;
362 struct nd_pfn_sb *pfn_sb;
363 struct pmem_device *pmem;
364 phys_addr_t offset;
365 int rc;
366 struct vmem_altmap __altmap = {
> 367 .base_pfn = __phys_to_pfn(nsio->res.start),
368 .reserve = __phys_to_pfn(SZ_8K),
369 };
370
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 44880 bytes --]
next reply other threads:[~2016-03-06 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 13:05 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-28 11:29 kbuild test robot
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=201603062121.s1ZUEjOS%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
/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