From: kbuild test robot <lkp@intel.com>
To: Peng Xu <pxu@codeaurora.org>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>,
Sara Sharon <sara.sharon@intel.com>,
Jouni Malinen <jouni@codeaurora.org>
Subject: [mac80211-next:cfg80211-mac80211-multi-bssid 8/20] ERROR: "__umoddi3" [net/wireless/cfg80211.ko] undefined!
Date: Sat, 9 Feb 2019 15:47:01 +0800 [thread overview]
Message-ID: <201902091559.zMnqaexs%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git cfg80211-mac80211-multi-bssid
head: 851ae31d34063deb1eae49f5d797a12a5557e832
commit: 0b8fb8235be8be99a197e8d948fc0a2df8dc261a [8/20] cfg80211: Parsing of Multiple BSSID information in scanning
config: i386-randconfig-x0-02091211 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
git checkout 0b8fb8235be8be99a197e8d948fc0a2df8dc261a
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> ERROR: "__umoddi3" [net/wireless/cfg80211.ko] undefined!
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33212 bytes --]
next reply other threads:[~2019-02-09 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 7:47 kbuild test robot [this message]
2019-02-09 8:08 ` [mac80211-next:cfg80211-mac80211-multi-bssid 8/20] ERROR: "__umoddi3" [net/wireless/cfg80211.ko] undefined! Johannes Berg
2019-02-11 14:57 ` Jouni Malinen
2019-02-11 14:58 ` Johannes Berg
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=201902091559.zMnqaexs%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=jouni@codeaurora.org \
--cc=kbuild-all@01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pxu@codeaurora.org \
--cc=sara.sharon@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).