From: kernel test robot <lkp@intel.com>
To: Jessica Yu <jeyu@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: ERROR: modpost: "__mulsi3" undefined!
Date: Fri, 19 Jun 2020 19:10:04 +0800 [thread overview]
Message-ID: <202006191901.2KhWzpN8%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Hi Jessica,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 5e857ce6eae7ca21b2055cca4885545e29228fe2
commit: 93c95e526a4ef00eb3d5a1e0920ba5a22f32e40d modpost: rework and consolidate logging interface
date: 3 months ago
config: nios2-randconfig-c003-20200619 (attached as .config)
compiler: nios2-linux-gcc (GCC) 9.3.0
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: "__mulsi3" [net/sunrpc/auth_gss/auth_rpcgss.ko] undefined!
ERROR: modpost: "__mulsi3" [fs/cifs/cifs.ko] undefined!
ERROR: modpost: "__mulsi3" [fs/nfs/nfsv4.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25208 bytes --]
next reply other threads:[~2020-06-19 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 11:10 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-19 11:44 ERROR: modpost: "__mulsi3" undefined! kernel test robot
2020-06-19 16:17 kernel test robot
2020-06-20 6:41 ` Denis Efremov
2020-06-20 8:38 kernel test robot
2020-06-21 0:58 kernel test robot
2020-06-21 1:32 kernel test robot
2020-06-21 3:35 kernel test robot
2020-06-21 5:49 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=202006191901.2KhWzpN8%lkp@intel.com \
--to=lkp@intel.com \
--cc=jeyu@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox