From: kbuild test robot <lkp@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 18/317] mm/vmscan.c:2966:14: error: implicit declaration of function 'lruvec_page_state_local'; did you mean 'lruvec_page_state'?
Date: Wed, 17 Apr 2019 14:44:23 +0800 [thread overview]
Message-ID: <201904171421.wplvKXWT%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: def6be39d5629b938faba788330db817d19a04da
commit: 7e0f45f540683e6312df0cfbcf0c703f35fcf763 [18/317] mm: fix inactive list balancing between NUMA nodes and cgroups
config: riscv-tinyconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 8.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 7e0f45f540683e6312df0cfbcf0c703f35fcf763
# save the attached .config to linux build tree
GCC_VERSION=8.1.0 make.cross ARCH=riscv
Note: the mmotm/master HEAD def6be39d5629b938faba788330db817d19a04da builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
mm/vmscan.c: In function 'snapshot_refaults':
>> mm/vmscan.c:2966:14: error: implicit declaration of function 'lruvec_page_state_local'; did you mean 'lruvec_page_state'? [-Werror=implicit-function-declaration]
refaults = lruvec_page_state_local(lruvec, WORKINGSET_ACTIVATE);
^~~~~~~~~~~~~~~~~~~~~~~
lruvec_page_state
cc1: some warnings being treated as errors
vim +2966 mm/vmscan.c
2955
2956 static void snapshot_refaults(struct mem_cgroup *root_memcg, pg_data_t *pgdat)
2957 {
2958 struct mem_cgroup *memcg;
2959
2960 memcg = mem_cgroup_iter(root_memcg, NULL, NULL);
2961 do {
2962 unsigned long refaults;
2963 struct lruvec *lruvec;
2964
2965 lruvec = mem_cgroup_lruvec(pgdat, memcg);
> 2966 refaults = lruvec_page_state_local(lruvec, WORKINGSET_ACTIVATE);
2967 lruvec->refaults = refaults;
2968 } while ((memcg = mem_cgroup_iter(root_memcg, memcg, NULL)));
2969 }
2970
---
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: 4624 bytes --]
reply other threads:[~2019-04-17 6:45 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=201904171421.wplvKXWT%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox