From: kernel test robot <lkp@intel.com>
To: Jianmin Lv <lvjianmin@loongson.cn>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Marc Zyngier <maz@kernel.org>
Subject: [linux-next:master 11562/12552] irq-loongarch-cpu.c:undefined reference to `pch_pic_handle'
Date: Sat, 23 Jul 2022 01:46:11 +0800 [thread overview]
Message-ID: <202207230124.UN2SWAeP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 18c107a1f120d095404d141dfad8f594bdc44020
commit: e8bba72b396cef7c919c73710f3c5884521adb4e [11562/12552] irqchip / ACPI: Introduce ACPI_IRQ_MODEL_LPIC for LoongArch
config: loongarch-randconfig-r035-20220722 (https://download.01.org/0day-ci/archive/20220723/202207230124.UN2SWAeP-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.1.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=e8bba72b396cef7c919c73710f3c5884521adb4e
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 e8bba72b396cef7c919c73710f3c5884521adb4e
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=loongarch SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
loongarch64-linux-ld: arch/loongarch/kernel/env.o: in function `init_environ':
env.c:(.init.text+0x120): undefined reference to `efi'
loongarch64-linux-ld: env.c:(.init.text+0x124): undefined reference to `efi'
loongarch64-linux-ld: env.c:(.init.text+0x124): undefined reference to `efi'
loongarch64-linux-ld: env.c:(.init.text+0x154): undefined reference to `efi_get_fdt_params'
loongarch64-linux-ld: env.c:(.init.text+0x16c): undefined reference to `efi_memmap_init_early'
loongarch64-linux-ld: arch/loongarch/kernel/setup.o: in function `.L8':
setup.c:(.init.text+0x108): undefined reference to `efi'
loongarch64-linux-ld: setup.c:(.init.text+0x10c): undefined reference to `efi'
loongarch64-linux-ld: setup.c:(.init.text+0x10c): undefined reference to `efi'
loongarch64-linux-ld: arch/loongarch/kernel/setup.o: in function `platform_init':
setup.c:(.init.text+0x668): undefined reference to `efi_init'
loongarch64-linux-ld: setup.c:(.init.text+0x6fc): undefined reference to `efi_runtime_init'
loongarch64-linux-ld: arch/loongarch/kernel/mem.o: in function `memblock_init':
mem.c:(.init.text+0x24): undefined reference to `efi'
loongarch64-linux-ld: mem.c:(.init.text+0x28): undefined reference to `efi'
loongarch64-linux-ld: mem.c:(.init.text+0x28): undefined reference to `efi'
loongarch64-linux-ld: arch/loongarch/kernel/numa.o: in function `.L34':
numa.c:(.init.text+0x290): undefined reference to `efi'
loongarch64-linux-ld: numa.c:(.init.text+0x294): undefined reference to `efi'
loongarch64-linux-ld: arch/loongarch/kernel/numa.o:numa.c:(.init.text+0x294): more undefined references to `efi' follow
loongarch64-linux-ld: drivers/irqchip/irq-loongarch-cpu.o: in function `.L13':
irq-loongarch-cpu.c:(.text+0x98): undefined reference to `find_pch_pic'
loongarch64-linux-ld: drivers/irqchip/irq-loongarch-cpu.o: in function `.L11':
>> irq-loongarch-cpu.c:(.text+0xac): undefined reference to `pch_pic_handle'
loongarch64-linux-ld: irq-loongarch-cpu.c:(.text+0xb0): undefined reference to `pch_pic_handle'
loongarch64-linux-ld: irq-loongarch-cpu.c:(.text+0xb0): undefined reference to `pch_pic_handle'
loongarch64-linux-ld: drivers/irqchip/irq-loongson-eiointc.o: in function `.L51':
irq-loongson-eiointc.c:(.init.text+0x90): undefined reference to `pch_pic_acpi_init'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-22 17:46 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=202207230124.UN2SWAeP-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lvjianmin@loongson.cn \
--cc=maz@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).