From: "Pali Rohár" <pali@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>
Subject: Re: [linux-next:master 3384/12117] pci.c:undefined reference to `pci_remap_iospace'
Date: Thu, 13 Jan 2022 14:49:38 +0100 [thread overview]
Message-ID: <20220113134938.3tx7iiukphvazvsq@pali> (raw)
In-Reply-To: <202201131529.A2s7rKQc-lkp@intel.com>
On Thursday 13 January 2022 16:04:46 kernel test robot wrote:
> Hi Pali,
>
> FYI, the error/warning still remains.
See: https://lore.kernel.org/linux-mm/20211204022131.bmhla4gkph7s7hy2@pali/
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 27c9d5b3c24af29de643533984f1ba3e650c7c78
> commit: bc02973a06a6c74374edeb6d73ed4bde99b37456 [3384/12117] arm: ioremap: Implement standard PCI function pci_remap_iospace()
> config: arm-randconfig-r004-20220113 (https://download.01.org/0day-ci/archive/20220113/202201131529.A2s7rKQc-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-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/next/linux-next.git/commit/?id=bc02973a06a6c74374edeb6d73ed4bde99b37456
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout bc02973a06a6c74374edeb6d73ed4bde99b37456
> # 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=arm 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 >>):
>
> arm-linux-gnueabi-ld: arch/arm/mach-dove/pcie.o: in function `dove_pcie_setup':
> pcie.c:(.init.text+0x160): undefined reference to `pci_ioremap_io'
> arm-linux-gnueabi-ld: drivers/pci/pci.o: in function `devm_pci_remap_iospace':
> >> pci.c:(.text+0x4e48): undefined reference to `pci_remap_iospace'
> arm-linux-gnueabi-ld: drivers/pci/controller/pci-mvebu.o: in function `mvebu_pcie_probe':
> pci-mvebu.c:(.text+0x1408): undefined reference to `pci_ioremap_io'
>
> ---
> 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: Pali Rohár <pali@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 3384/12117] pci.c:undefined reference to `pci_remap_iospace'
Date: Thu, 13 Jan 2022 14:49:38 +0100 [thread overview]
Message-ID: <20220113134938.3tx7iiukphvazvsq@pali> (raw)
In-Reply-To: <202201131529.A2s7rKQc-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]
On Thursday 13 January 2022 16:04:46 kernel test robot wrote:
> Hi Pali,
>
> FYI, the error/warning still remains.
See: https://lore.kernel.org/linux-mm/20211204022131.bmhla4gkph7s7hy2(a)pali/
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 27c9d5b3c24af29de643533984f1ba3e650c7c78
> commit: bc02973a06a6c74374edeb6d73ed4bde99b37456 [3384/12117] arm: ioremap: Implement standard PCI function pci_remap_iospace()
> config: arm-randconfig-r004-20220113 (https://download.01.org/0day-ci/archive/20220113/202201131529.A2s7rKQc-lkp(a)intel.com/config)
> compiler: arm-linux-gnueabi-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/next/linux-next.git/commit/?id=bc02973a06a6c74374edeb6d73ed4bde99b37456
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout bc02973a06a6c74374edeb6d73ed4bde99b37456
> # 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=arm 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 >>):
>
> arm-linux-gnueabi-ld: arch/arm/mach-dove/pcie.o: in function `dove_pcie_setup':
> pcie.c:(.init.text+0x160): undefined reference to `pci_ioremap_io'
> arm-linux-gnueabi-ld: drivers/pci/pci.o: in function `devm_pci_remap_iospace':
> >> pci.c:(.text+0x4e48): undefined reference to `pci_remap_iospace'
> arm-linux-gnueabi-ld: drivers/pci/controller/pci-mvebu.o: in function `mvebu_pcie_probe':
> pci-mvebu.c:(.text+0x1408): undefined reference to `pci_ioremap_io'
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2022-01-13 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 8:04 [linux-next:master 3384/12117] pci.c:undefined reference to `pci_remap_iospace' kernel test robot
2022-01-13 8:04 ` kernel test robot
2022-01-13 13:49 ` Pali Rohár [this message]
2022-01-13 13:49 ` Pali Rohár
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=20220113134938.3tx7iiukphvazvsq@pali \
--to=pali@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=rmk+kernel@armlinux.org.uk \
/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.