From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: ERROR: modpost: "__netdev_update_features" [drivers/net/bonding/bonding.ko] undefined!
Date: Wed, 20 May 2026 23:20:29 +0200 [thread overview]
Message-ID: <202605202332.QJE5bHVo-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jihong Min <hurryman2212@gmail.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Jihong-Min/xfrm-add-a-lower-device-offload-handle-resolver/20260520-162948
head: bcd1877590171e39d1afa5918b534f20a01d0506
commit: 79f3bc097e51b114682d9dea7428053cf6cbb955 bonding: expose user-controlled IPsec features for LAG
date: 13 hours ago
:::::: branch date: 13 hours ago
:::::: commit date: 13 hours ago
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260520/202605202332.QJE5bHVo-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260520/202605202332.QJE5bHVo-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/202605202332.QJE5bHVo-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "__netdev_update_features" [drivers/net/bonding/bonding.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-05-20 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 21:20 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-21 7:47 ERROR: modpost: "__netdev_update_features" [drivers/net/bonding/bonding.ko] undefined! kernel test robot
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=202605202332.QJE5bHVo-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.