From: kernel test robot <lkp@intel.com>
To: Joe Thornber <ejt@redhat.com>
Cc: dm-devel@redhat.com, Mike Snitzer <snitzer@kernel.org>,
oe-kbuild-all@lists.linux.dev
Subject: [dm-devel] [device-mapper-dm:for-next 2/4] dm-extent-allocator.c:undefined reference to `__udivdi3'
Date: Fri, 15 Sep 2023 20:25:33 +0800 [thread overview]
Message-ID: <202309152007.7euOF5Fr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
head: df3f51f6ca53e525420cd4cf4c7d9f5cabe9a29e
commit: b97bcee4b9999c9f5aadc06317ade18c5cbe37f6 [2/4] dm persistent data: Introduce extent allocator
config: i386-buildonly-randconfig-004-20230915 (https://download.01.org/0day-ci/archive/20230915/202309152007.7euOF5Fr-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230915/202309152007.7euOF5Fr-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/202309152007.7euOF5Fr-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: drivers/md/persistent-data/dm-extent-allocator.o: in function `dm_alloc_context_alloc':
>> dm-extent-allocator.c:(.text+0x773): undefined reference to `__udivdi3'
>> ld: dm-extent-allocator.c:(.text+0x791): undefined reference to `__udivdi3'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
reply other threads:[~2023-09-15 12:26 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=202309152007.7euOF5Fr-lkp@intel.com \
--to=lkp@intel.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=snitzer@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