From: kernel test robot <lkp@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jarkko-tpmdd:v4l2-loopback-dev 18/18] ld.lld: error: undefined symbol: __aeabi_ldivmod
Date: Sun, 24 Nov 2024 22:31:39 +0800 [thread overview]
Message-ID: <202411242226.LIJS1y07-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git v4l2-loopback-dev
head: 36ae93bcb2d7a7e6d13533fb976c545fc85bdee8
commit: 36ae93bcb2d7a7e6d13533fb976c545fc85bdee8 [18/18] media: v4l2-loopback: Remove v4l2l_mod64()
config: arm-randconfig-002-20241124 (https://download.01.org/0day-ci/archive/20241124/202411242226.LIJS1y07-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241124/202411242226.LIJS1y07-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411242226.LIJS1y07-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: __aeabi_ldivmod
>>> referenced by v4l2-loopback.c:2008 (drivers/media/v4l2-core/v4l2-loopback.c:2008)
>>> drivers/media/v4l2-core/v4l2-loopback.o:(v4l2_loopback_write) in archive vmlinux.a
>>> referenced by v4l2-loopback.c:1512 (drivers/media/v4l2-core/v4l2-loopback.c:1512)
>>> drivers/media/v4l2-core/v4l2-loopback.o:(get_capture_buffer) in archive vmlinux.a
>>> referenced by v4l2-loopback.c:1519 (drivers/media/v4l2-core/v4l2-loopback.c:1519)
>>> drivers/media/v4l2-core/v4l2-loopback.o:(get_capture_buffer) in archive vmlinux.a
>>> referenced 2 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-24 14:32 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=202411242226.LIJS1y07-lkp@intel.com \
--to=lkp@intel.com \
--cc=jarkko@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.