From: kernel test robot <lkp@intel.com>
To: David Woodhouse <dwmw@amazon.co.uk>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dwmw2:ffclock 39/44] undefined reference to `__moddi3'
Date: Thu, 21 May 2026 13:50:01 +0800 [thread overview]
Message-ID: <202605211351.eEeQALti-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/dwmw2/linux ffclock
head: 0351afde272ddc6e1f1312297a5e084c598ff4b0
commit: fef91959721b929cc114e9a4f8f9af4e73ddaa4a [39/44] timekeeping: Drive time_offset skew via per-tick ntp_error transfer
config: microblaze-allnoconfig (https://download.01.org/0day-ci/archive/20260521/202605211351.eEeQALti-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260521/202605211351.eEeQALti-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/202605211351.eEeQALti-lkp@intel.com/
All errors (new ones prefixed by >>):
microblaze-linux-ld: kernel/time/ntp.o: in function `second_overflow':
>> (.text+0x11e4): undefined reference to `__moddi3'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-21 5:51 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=202605211351.eEeQALti-lkp@intel.com \
--to=lkp@intel.com \
--cc=dwmw@amazon.co.uk \
--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.