From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 4714/7050] uv.c:undefined reference to `uv_info'
Date: Mon, 9 Mar 2020 08:26:09 +0800 [thread overview]
Message-ID: <202003090807.yDa3cYj0%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b86a6a241b7c60ca7a6ca4fb3c0d2aedbbf2c1b6
commit: a0f60f8431999bf57cf53c3b27c47ef156b4fa17 [4714/7050] s390/protvirt: Add sysfs firmware interface for Ultravisor information
config: s390-randconfig-a001-20200308 (attached as .config)
compiler: s390-linux-gcc (GCC) 7.5.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 a0f60f8431999bf57cf53c3b27c47ef156b4fa17
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=s390
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/s390/kernel/uv.o: In function `uv_query_max_guest_addr':
>> uv.c:(.text+0xc): undefined reference to `uv_info'
uv.c:(.text+0x40): undefined reference to `uv_info'
uv.c:(.text+0x72): undefined reference to `uv_info'
arch/s390/kernel/uv.o: In function `uv_query_max_guest_vms':
uv.c:(.text+0x8c): undefined reference to `uv_info'
uv.c:(.text+0xde): undefined reference to `uv_info'
arch/s390/kernel/uv.o:uv.c:(.text+0x11c): more undefined references to `uv_info' follow
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36640 bytes --]
reply other threads:[~2020-03-09 0:26 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=202003090807.yDa3cYj0%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.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