From: kbuild test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [tip:WIP.x86/mm 32/33] percpu.c:undefined reference to `is_vmalloc_addr'
Date: Fri, 29 Nov 2019 02:56:38 +0800 [thread overview]
Message-ID: <201911290224.2T3sN6OH%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/mm
head: 7ccd25bd603f0d08a967467f8d676e2263382506
commit: 7acc8323e483d980de07ff2e4c4906cc3e77d59c [32/33] mm, x86/mm: Untangle address space layout definitions from basic pgtable type definitions
config: c6x-evmc6678_defconfig (attached as .config)
compiler: c6x-elf-gcc (GCC) 7.4.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 7acc8323e483d980de07ff2e4c4906cc3e77d59c
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=c6x
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mm/percpu.o: In function `per_cpu_ptr_to_phys':
>> percpu.c:(.text+0x2760): undefined reference to `is_vmalloc_addr'
block/bio.o: In function `bio_map_kern':
>> bio.c:(.text+0x2d88): undefined reference to `is_vmalloc_addr'
kernel/iomem.o: In function `memunmap':
>> iomem.c:(.text+0x14): undefined reference to `is_vmalloc_addr'
kernel/iomem.o: In function `devm_memremap_release':
iomem.c:(.text+0x30): undefined reference to `is_vmalloc_addr'
mm/util.o: In function `kvfree':
>> util.c:(.text+0x774): undefined reference to `is_vmalloc_addr'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6002 bytes --]
reply other threads:[~2019-11-28 18:59 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=201911290224.2T3sN6OH%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®