From: kernel test robot <lkp@intel.com>
To: Tianyu Lan <Tianyu.Lan@microsoft.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Wei Liu <wei.liu@kernel.org>,
Michael Kelley <mikelley@microsoft.com>
Subject: [hyperv:hyperv-next 1/7] swiotlb.c:undefined reference to `memremap'
Date: Thu, 30 Dec 2021 09:17:27 +0800 [thread overview]
Message-ID: <202112300919.vfQIU5rt-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git hyperv-next
head: e1878402ab2dca12d1426f2fea39757943f3332c
commit: 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 [1/7] swiotlb: Add swiotlb bounce buffer remap function for HV IVM
config: s390-randconfig-r014-20211230 (https://download.01.org/0day-ci/archive/20211230/202112300919.vfQIU5rt-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=1a5e91d8375fc8369207cc0b9894a324f2bbf1d9
git remote add hyperv https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git
git fetch --no-tags hyperv hyperv-next
git checkout 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
s390-linux-ld: kernel/dma/swiotlb.o: in function `swiotlb_update_mem_attributes':
>> swiotlb.c:(.init.text+0x314): undefined reference to `memremap'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hyperv:hyperv-next 1/7] swiotlb.c:undefined reference to `memremap'
Date: Thu, 30 Dec 2021 09:17:27 +0800 [thread overview]
Message-ID: <202112300919.vfQIU5rt-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git hyperv-next
head: e1878402ab2dca12d1426f2fea39757943f3332c
commit: 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 [1/7] swiotlb: Add swiotlb bounce buffer remap function for HV IVM
config: s390-randconfig-r014-20211230 (https://download.01.org/0day-ci/archive/20211230/202112300919.vfQIU5rt-lkp(a)intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=1a5e91d8375fc8369207cc0b9894a324f2bbf1d9
git remote add hyperv https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git
git fetch --no-tags hyperv hyperv-next
git checkout 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
s390-linux-ld: kernel/dma/swiotlb.o: in function `swiotlb_update_mem_attributes':
>> swiotlb.c:(.init.text+0x314): undefined reference to `memremap'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2021-12-30 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 1:17 kernel test robot [this message]
2021-12-30 1:17 ` [hyperv:hyperv-next 1/7] swiotlb.c:undefined reference to `memremap' kernel test robot
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=202112300919.vfQIU5rt-lkp@intel.com \
--to=lkp@intel.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=wei.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.