From: kbuild test robot <lkp@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [vireshk-pm:opp/qcom-fix 8485/8905] mm/vmacache.c:127:26: error: 'addr' undeclared
Date: Wed, 12 Sep 2018 21:34:07 +0800 [thread overview]
Message-ID: <201809122101.Dp3P2SWZ%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git opp/qcom-fix
head: e570c000d1f81e380c9b8919fd84e215471f6cb9
commit: 5d2f33872046e7ffdd62dd80472cd466ea8407ac [8485/8905] mm, vmacache: hash addresses based on pmd
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.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 5d2f33872046e7ffdd62dd80472cd466ea8407ac
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=sh
All errors (new ones prefixed by >>):
mm/vmacache.c: In function 'vmacache_find_exact':
>> mm/vmacache.c:127:26: error: 'addr' undeclared (first use in this function)
int idx = VMACACHE_HASH(addr);
^
mm/vmacache.c:14:31: note: in definition of macro 'VMACACHE_HASH'
#define VMACACHE_HASH(addr) ((addr >> PMD_SHIFT) & VMACACHE_MASK)
^~~~
mm/vmacache.c:127:26: note: each undeclared identifier is reported only once for each function it appears in
int idx = VMACACHE_HASH(addr);
^
mm/vmacache.c:14:31: note: in definition of macro 'VMACACHE_HASH'
#define VMACACHE_HASH(addr) ((addr >> PMD_SHIFT) & VMACACHE_MASK)
^~~~
vim +/addr +127 mm/vmacache.c
121
122 #ifndef CONFIG_MMU
123 struct vm_area_struct *vmacache_find_exact(struct mm_struct *mm,
124 unsigned long start,
125 unsigned long end)
126 {
> 127 int idx = VMACACHE_HASH(addr);
---
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: 48595 bytes --]
reply other threads:[~2018-09-12 13:34 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=201809122101.Dp3P2SWZ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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