LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Anand Ashok Dumbre <anand.ashok.dumbre@xilinx.com>,
linux-kernel@vger.kernel.org, jic23@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, git@xilinx.com,
michal.simek@xilinx.com, gregkh@linuxfoundation.org,
rafael@kernel.org, linux-acpi@vger.kernel.org,
andriy.shevchenko@linux.intel.com
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v11 1/5] device property: Add fwnode_iomap()
Date: Sat, 27 Nov 2021 19:54:56 +0800 [thread overview]
Message-ID: <202111271953.N5Nm1MIG-lkp@intel.com> (raw)
In-Reply-To: <20211124225407.17793-2-anand.ashok.dumbre@xilinx.com>
Hi Anand,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on jic23-iio/togreg]
[also build test ERROR on xilinx-xlnx/master linux/master linus/master v5.16-rc2 next-20211126]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Anand-Ashok-Dumbre/Add-Xilinx-AMS-Driver/20211125-065614
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: s390-randconfig-r044-20211126 (https://download.01.org/0day-ci/archive/20211127/202111271953.N5Nm1MIG-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://github.com/0day-ci/linux/commit/b9acba7c202b47024781ea7a6f85b787df15f29b
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Anand-Ashok-Dumbre/Add-Xilinx-AMS-Driver/20211125-065614
git checkout b9acba7c202b47024781ea7a6f85b787df15f29b
# 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/coherent.o: in function `dma_init_coherent_memory':
coherent.c:(.text+0x6c): undefined reference to `memremap'
s390-linux-ld: coherent.c:(.text+0x106): undefined reference to `memunmap'
s390-linux-ld: kernel/dma/coherent.o: in function `dma_declare_coherent_memory':
coherent.c:(.text+0x436): undefined reference to `memunmap'
s390-linux-ld: drivers/irqchip/irq-al-fic.o: in function `al_fic_init_dt':
irq-al-fic.c:(.init.text+0x28): undefined reference to `of_iomap'
s390-linux-ld: irq-al-fic.c:(.init.text+0x1f4): undefined reference to `iounmap'
s390-linux-ld: drivers/dma/idma64.o: in function `idma64_platform_probe':
idma64.c:(.text+0x14cc): undefined reference to `devm_ioremap_resource'
s390-linux-ld: drivers/tty/ipwireless/main.o: in function `ipwireless_detach':
main.c:(.text+0x8a): undefined reference to `iounmap'
s390-linux-ld: main.c:(.text+0xd0): undefined reference to `iounmap'
s390-linux-ld: drivers/tty/ipwireless/main.o: in function `ipwireless_probe':
main.c:(.text+0x258): undefined reference to `ioremap'
s390-linux-ld: main.c:(.text+0x30c): undefined reference to `ioremap'
s390-linux-ld: main.c:(.text+0x35e): undefined reference to `iounmap'
s390-linux-ld: main.c:(.text+0x3a0): undefined reference to `iounmap'
s390-linux-ld: drivers/tty/ipwireless/main.o: in function `config_ipwireless':
main.c:(.text+0x5a0): undefined reference to `iounmap'
s390-linux-ld: main.c:(.text+0x5e0): undefined reference to `iounmap'
s390-linux-ld: drivers/base/property.o: in function `fwnode_iomap':
>> property.c:(.text+0xf36): undefined reference to `of_iomap'
s390-linux-ld: drivers/net/arcnet/arc-rimi.o: in function `arc_rimi_exit':
arc-rimi.c:(.exit.text+0x34): undefined reference to `iounmap'
s390-linux-ld: drivers/net/arcnet/arc-rimi.o: in function `arcrimi_found':
arc-rimi.c:(.init.text+0xce): undefined reference to `ioremap'
s390-linux-ld: arc-rimi.c:(.init.text+0x14c): undefined reference to `iounmap'
s390-linux-ld: arc-rimi.c:(.init.text+0x2b0): undefined reference to `iounmap'
s390-linux-ld: arc-rimi.c:(.init.text+0x332): undefined reference to `ioremap'
s390-linux-ld: arc-rimi.c:(.init.text+0x3f4): undefined reference to `iounmap'
s390-linux-ld: drivers/net/arcnet/arc-rimi.o: in function `check_mirror':
arc-rimi.c:(.text.unlikely+0x4e): undefined reference to `ioremap'
s390-linux-ld: arc-rimi.c:(.text.unlikely+0x74): undefined reference to `iounmap'
s390-linux-ld: drivers/net/ethernet/8390/pcnet_cs.o: in function `pcnet_release':
pcnet_cs.c:(.text+0x6b8): undefined reference to `iounmap'
s390-linux-ld: drivers/net/ethernet/8390/pcnet_cs.o: in function `setup_shmem_window':
pcnet_cs.c:(.text+0xb44): undefined reference to `ioremap'
s390-linux-ld: pcnet_cs.c:(.text+0xbd8): undefined reference to `iounmap'
s390-linux-ld: drivers/net/ethernet/8390/pcnet_cs.o: in function `get_hwinfo':
pcnet_cs.c:(.text+0x1558): undefined reference to `ioremap'
s390-linux-ld: pcnet_cs.c:(.text+0x1656): undefined reference to `iounmap'
s390-linux-ld: drivers/net/ethernet/xircom/xirc2ps_cs.o: in function `xirc2ps_release':
xirc2ps_cs.c:(.text+0x518): undefined reference to `iounmap'
s390-linux-ld: drivers/net/ethernet/xircom/xirc2ps_cs.o: in function `xirc2ps_config':
xirc2ps_cs.c:(.text+0x1584): undefined reference to `ioremap'
s390-linux-ld: drivers/pcmcia/cistpl.o: in function `set_cis_map':
cistpl.c:(.text+0x5c6): undefined reference to `ioremap'
s390-linux-ld: cistpl.c:(.text+0x5fc): undefined reference to `iounmap'
s390-linux-ld: cistpl.c:(.text+0x62a): undefined reference to `iounmap'
s390-linux-ld: cistpl.c:(.text+0x63c): undefined reference to `ioremap'
s390-linux-ld: drivers/pcmcia/cistpl.o: in function `release_cis_mem':
cistpl.c:(.text+0xf80): undefined reference to `iounmap'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-11-27 11:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 22:54 [PATCH v11 0/5] Add Xilinx AMS Driver Anand Ashok Dumbre
2021-11-24 22:54 ` [PATCH v11 1/5] device property: Add fwnode_iomap() Anand Ashok Dumbre
2021-11-25 11:42 ` Andy Shevchenko
2021-11-30 21:58 ` Anand Ashok Dumbre
2021-12-02 9:10 ` Anand Ashok Dumbre
2021-12-02 9:37 ` Andy Shevchenko
2021-12-02 11:46 ` Anand Ashok Dumbre
2021-12-02 12:34 ` Anand Ashok Dumbre
2021-11-27 11:54 ` kernel test robot [this message]
2021-11-24 22:54 ` [PATCH v11 2/5] arm64: zynqmp: DT: Add Xilinx AMS node Anand Ashok Dumbre
2021-11-24 22:54 ` [PATCH v11 3/5] iio: adc: Add Xilinx AMS driver Anand Ashok Dumbre
2021-11-25 12:14 ` Andy Shevchenko
2021-12-02 16:32 ` Anand Ashok Dumbre
2021-12-02 16:51 ` Andy Shevchenko
2021-11-27 2:43 ` kernel test robot
2021-11-27 17:50 ` Jonathan Cameron
2021-11-27 5:16 ` kernel test robot
2021-11-24 22:54 ` [PATCH v11 4/5] dt-bindings: iio: adc: Add Xilinx AMS binding documentation Anand Ashok Dumbre
2021-11-24 22:54 ` [PATCH v11 5/5] MAINTAINERS: Add maintainer for xilinx-ams Anand Ashok Dumbre
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=202111271953.N5Nm1MIG-lkp@intel.com \
--to=lkp@intel.com \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=git@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lars@metafoo.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).