All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen:5.15/bbr2 14/28] ERROR: modpost: "__divdi3" [net/ipv4/tcp_bbr.ko] undefined!
Date: Sun, 07 Nov 2021 19:30:37 +0800	[thread overview]
Message-ID: <202111071929.ba2aQ5xQ-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]

tree:   https://github.com/zen-kernel/zen-kernel 5.15/bbr2
head:   de136008f854ed5dd68ee7b7f65ba23c2df6b960
commit: 16b8d7dfec9d9f7b8d182e58148af031bd2c4afa [14/28] net-tcp: re-generalize TSO sizing in TCP CC module API
config: i386-debian-10.3 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/zen-kernel/zen-kernel/commit/16b8d7dfec9d9f7b8d182e58148af031bd2c4afa
        git remote add zen https://github.com/zen-kernel/zen-kernel
        git fetch --no-tags zen 5.15/bbr2
        git checkout 16b8d7dfec9d9f7b8d182e58148af031bd2c4afa
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>, old ones prefixed by <<):

>> ERROR: modpost: "__divdi3" [net/ipv4/tcp_bbr.ko] undefined!
>> ERROR: modpost: "__udivdi3" [net/ipv4/tcp_bbr.ko] undefined!

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34089 bytes --]

                 reply	other threads:[~2021-11-07 11:30 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=202111071929.ba2aQ5xQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.