From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [saeed:net-mlx5 2/6] ERROR: modpost: "__udivdi3" undefined!
Date: Mon, 25 Jan 2021 07:50:28 +0800 [thread overview]
Message-ID: <202101250722.f48IfPW2-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git net-mlx5
head: 392050b7d0edd96ef23711cd2c6bcfb1c9a740f4
commit: e33eda6344813b2f2acde1a0f6b6457a3bcf40e7 [2/6] net/mlx5e: E-switch, Fix rate calculation for overflow
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/commit/?id=e33eda6344813b2f2acde1a0f6b6457a3bcf40e7
git remote add saeed https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
git fetch --no-tags saeed net-mlx5
git checkout e33eda6344813b2f2acde1a0f6b6457a3bcf40e7
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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: "__udivdi3" [drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.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: 69829 bytes --]
reply other threads:[~2021-01-24 23:50 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=202101250722.f48IfPW2-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.