From: kernel test robot <lkp@intel.com>
To: Kelvin Zhang <zhangxp1998@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, Chao Yu <chao@kernel.org>
Subject: [chao:feature/subpage 9/10] file.c:undefined reference to `__divdi3'
Date: Sun, 30 Aug 2026 23:16:56 +0800 [thread overview]
Message-ID: <202608302349.AXJE2LxU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git feature/subpage
head: 3a537197e7b9327a386b4c5deab273a387072d1f
commit: 7967e8f5c2c2f347acdc20281027d28c46b8a9e1 [9/10] f2fs: parameterize block size and mask macros
config: sh-randconfig-r071-20260830 (https://download.01.org/0day-ci/archive/20260830/202608302349.AXJE2LxU-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 16.1.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260830/202608302349.AXJE2LxU-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/202608302349.AXJE2LxU-lkp@intel.com/
All errors (new ones prefixed by >>):
sh4-linux-ld: fs/f2fs/file.o: in function `f2fs_sec_trim_file':
>> file.c:(.text+0x3468): undefined reference to `__divdi3'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-08-30 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 15:16 kernel test robot [this message]
2026-08-31 4:58 ` [chao:feature/subpage 9/10] file.c:undefined reference to `__divdi3' Xinping Zhang
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=202608302349.AXJE2LxU-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhangxp1998@gmail.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.