From: kbuild test robot <fengguang.wu@intel.com>
To: Zi Yan <zi.yan@cs.rutgers.edu>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 56/204] include/linux/swapops.h:220:9: error: implicit declaration of function '__pmd'
Date: Mon, 14 Aug 2017 15:01:08 +0800 [thread overview]
Message-ID: <201708141500.5z0pcSam%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 16a1d38e82793981d3e8985ff21cea6ac93ba047
commit: 792804d6e8440cee5881a64104194661eff74148 [56/204] mm-thp-enable-thp-migration-in-generic-path-fix
config: sparc-defconfig (attached as .config)
compiler: sparc-linux-gcc (GCC) 6.2.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 792804d6e8440cee5881a64104194661eff74148
# save the attached .config to linux build tree
make.cross ARCH=sparc
All errors (new ones prefixed by >>):
In file included from mm/vmscan.c:55:0:
include/linux/swapops.h: In function 'swp_entry_to_pmd':
>> include/linux/swapops.h:220:9: error: implicit declaration of function '__pmd' [-Werror=implicit-function-declaration]
return __pmd(0);
^~~~~
>> include/linux/swapops.h:220:9: error: incompatible types when returning type 'int' but 'pmd_t {aka struct <anonymous>}' was expected
return __pmd(0);
^~~~~~~~
cc1: some warnings being treated as errors
vim +/__pmd +220 include/linux/swapops.h
217
218 static inline pmd_t swp_entry_to_pmd(swp_entry_t entry)
219 {
> 220 return __pmd(0);
221 }
222
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 12095 bytes --]
reply other threads:[~2017-08-14 7:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201708141500.5z0pcSam%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=zi.yan@cs.rutgers.edu \
/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).