From: kernel test robot <lkp@intel.com>
To: Qu Wenruo <wqu@suse.com>
Cc: oe-kbuild-all@lists.linux.dev, David Sterba <dsterba@suse.com>
Subject: [kdave:for-next 120/128] ERROR: modpost: "__aeabi_uldivmod" [fs/btrfs/btrfs.ko] undefined!
Date: Fri, 17 Feb 2023 20:53:42 +0800 [thread overview]
Message-ID: <202302172004.2bUI7Nec-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
head: 5c202ce4169d7220f67b0c8b3650f26ed5f9bcaf
commit: 4a8c6e8a6dc8ae4ce2adb1f807b61b6d99088293 [120/128] btrfs: replace btrfs_io_context::raid_map with a fixed u64 value
config: arm-randconfig-r023-20230214 (https://download.01.org/0day-ci/archive/20230217/202302172004.2bUI7Nec-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.1.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://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git/commit/?id=4a8c6e8a6dc8ae4ce2adb1f807b61b6d99088293
git remote add kdave https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
git fetch --no-tags kdave for-next
git checkout 4a8c6e8a6dc8ae4ce2adb1f807b61b6d99088293
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302172004.2bUI7Nec-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "__aeabi_uldivmod" [fs/btrfs/btrfs.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-17 12:54 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=202302172004.2bUI7Nec-lkp@intel.com \
--to=lkp@intel.com \
--cc=dsterba@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wqu@suse.com \
/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.