From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: ERROR: modpost: "__divdi3" [drivers/media/i2c/og0ve1b.ko] undefined!
Date: Thu, 30 Jul 2026 21:42:22 +0800 [thread overview]
Message-ID: <202607302129.4V2DiGMy-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/Wenmeng-Liu/dt-bindings-media-i2c-og0ve1b-Add-OmniVision-OG0VA1B-camera-sensor/20260730-165146, commit: 168839e90295cc189be153bc4a0a6d7f7362ff49"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
CC: 0day robot <lkp@intel.com>
CC: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
tree: https://github.com/intel-lab-lkp/linux/commits/Wenmeng-Liu/dt-bindings-media-i2c-og0ve1b-Add-OmniVision-OG0VA1B-camera-sensor/20260730-165146
head: 1a0c84403aa373a1df3a42ef86d07a881f24e9ca
commit: 168839e90295cc189be153bc4a0a6d7f7362ff49 media: i2c: og0ve1b: Introduce per-sensor data structure
date: 5 hours ago
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20260730/202607302129.4V2DiGMy-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260730/202607302129.4V2DiGMy-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/r/202607302129.4V2DiGMy-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "__divdi3" [drivers/media/i2c/og0ve1b.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-30 13:42 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=202607302129.4V2DiGMy-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.