From: kbuild test robot <lkp@intel.com>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 8475/9410] ERROR: "__vmalloc_node_range" [lib/test_vmalloc.ko] undefined!
Date: Tue, 19 Feb 2019 06:04:38 +0800 [thread overview]
Message-ID: <201902190637.nP67rDcw%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cb916fc5eabf8832e05f73c246eb467259846ef0
commit: bd7e49fa421950084fff786200b7fd6872d51643 [8475/9410] vmalloc: add test driver to analyse vmalloc allocator
config: h8300-allyesconfig (attached as .config)
compiler: h8300-linux-gcc (GCC) 8.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 bd7e49fa421950084fff786200b7fd6872d51643
# save the attached .config to linux build tree
GCC_VERSION=8.2.0 make.cross ARCH=h8300
All errors (new ones prefixed by >>):
ERROR: "__divdi3" [lib/test_vmalloc.ko] undefined!
>> ERROR: "__vmalloc_node_range" [lib/test_vmalloc.ko] undefined!
---
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: 48641 bytes --]
next reply other threads:[~2019-02-18 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:04 kbuild test robot [this message]
2019-02-19 8:54 ` Uladzislau Rezki
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=201902190637.nP67rDcw%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.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