From: kbuild test robot <lkp@intel•com>
To: Marc Zyngier <maz@kernel•org>
Cc: kbuild-all@01•org, linux-arm-kernel@lists•infradead.org
Subject: [arm-platforms:irq/gic-v4.1-devel 12/37] irq-gic-v3-its.c:undefined reference to `__aeabi_uldivmod'
Date: Thu, 26 Sep 2019 07:46:58 +0800 [thread overview]
Message-ID: <201909260757.CnSthRz2%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gic-v4.1-devel
head: d0930710fc52cf43ff23432ac6c2ac98b4a8e3b2
commit: 332496d87708d4c745a13687538661952928227f [12/37] irqchip/gic-v4.1: VPE table (aka GICR_VPROPBASER) allocation
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.4.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 332496d87708d4c745a13687538661952928227f
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel•com>
All errors (new ones prefixed by >>):
drivers/irqchip/irq-gic-v3-its.o: In function `its_cpu_init':
>> irq-gic-v3-its.c:(.text+0x6534): undefined reference to `__aeabi_uldivmod'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 71376 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-09-25 23:47 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=201909260757.CnSthRz2%lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=kbuild-all@01$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=maz@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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