From: Nam Cao <namcao@linutronix.de>
To: kernel test robot <lkp@intel.com>, Gabriele Monaco <gmonaco@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [trace:latency/for-next 33/38] ERROR: modpost: "__udivdi3" [kernel/trace/rv/rv_monitors_test.ko] undefined!
Date: Mon, 03 Aug 2026 08:58:55 +0200 [thread overview]
Message-ID: <87cxvzofkg.fsf@yellow.woof> (raw)
In-Reply-To: <202608020311.hYjqOG5k-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace latency/for-next
> head: 984b5a36fd12d1849511a45fda32036fe2b0d004
> commit: 8da2a88383658dac97769ed8f807ef6100a69480 [33/38] rv: Add KUnit tests for some DA/HA monitors
> config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20260802/202608020311.hYjqOG5k-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260802/202608020311.hYjqOG5k-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/202608020311.hYjqOG5k-lkp@intel.com/
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "__udivdi3" [kernel/trace/rv/rv_monitors_test.ko] undefined!
We could switch the division to div64_u64(), or we could change
deadline_thresh's type to u32.
Gabriele, can deadline_thresh fits in u32?
Nam
next prev parent reply other threads:[~2026-08-03 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 20:09 [trace:latency/for-next 33/38] ERROR: modpost: "__udivdi3" [kernel/trace/rv/rv_monitors_test.ko] undefined! kernel test robot
2026-08-03 6:58 ` Nam Cao [this message]
2026-08-03 7:44 ` Gabriele Monaco
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=87cxvzofkg.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=lkp@intel.com \
--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.