From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [thierryreding:for-5.14/work 65/66] hub.c:undefined reference to `__aeabi_uldivmod'
Date: Fri, 28 May 2021 09:29:31 +0800 [thread overview]
Message-ID: <202105280926.xt1dpsL6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
tree: https://github.com/thierryreding/linux for-5.14/work
head: 6a34089304a9d77ac8a29b08e0d9091719f2a9c9
commit: 9e69a33a82b7f325d17a55bb1fc70fac213c369c [65/66] drm/tegra: hub: Implement basic scaling support
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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/thierryreding/linux/commit/9e69a33a82b7f325d17a55bb1fc70fac213c369c
git remote add thierryreding https://github.com/thierryreding/linux
git fetch --no-tags thierryreding for-5.14/work
git checkout 9e69a33a82b7f325d17a55bb1fc70fac213c369c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
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: drivers/gpu/drm/tegra/hub.o: in function `tegra_shared_plane_atomic_update':
>> hub.c:(.text+0x1ab0): undefined reference to `__aeabi_uldivmod'
>> arm-linux-gnueabi-ld: hub.c:(.text+0x1b74): undefined reference to `__aeabi_uldivmod'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 54948 bytes --]
reply other threads:[~2021-05-28 1:29 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=202105280926.xt1dpsL6-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.