From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kdave-btrfs-devel:dev/scrub-bw-sysfs 102/102] ERROR: modpost: "__divdi3" undefined!
Date: Sat, 06 Feb 2021 05:45:58 +0800 [thread overview]
Message-ID: <202102060552.53sHp482-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
tree: https://github.com/kdave/btrfs-devel.git dev/scrub-bw-sysfs
head: 1139caf65b8afe72e9037879d61882e5b142b772
commit: 1139caf65b8afe72e9037879d61882e5b142b772 [102/102] btrfs: WIP scrub bandwidth control
config: m68k-q40_defconfig (attached as .config)
compiler: m68k-linux-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/kdave/btrfs-devel/commit/1139caf65b8afe72e9037879d61882e5b142b772
git remote add kdave-btrfs-devel https://github.com/kdave/btrfs-devel.git
git fetch --no-tags kdave-btrfs-devel dev/scrub-bw-sysfs
git checkout 1139caf65b8afe72e9037879d61882e5b142b772
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k
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 >>, old ones prefixed by <<):
ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
>> ERROR: modpost: "__divdi3" [fs/btrfs/btrfs.ko] undefined!
---
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: 14122 bytes --]
reply other threads:[~2021-02-05 21:45 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=202102060552.53sHp482-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.