linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sara Sharon <sara.sharon@intel.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org,
	Johannes Berg <johannes.berg@intel.com>
Subject: [mac80211-next:cfg80211-mac80211-multi-bssid 15/20] ERROR: "__umoddi3" [net/mac80211/mac80211.ko] undefined!
Date: Sat, 9 Feb 2019 06:03:31 +0800	[thread overview]
Message-ID: <201902090629.X9SzLP26%fengguang.wu@intel.com> (raw)

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

Hi Sara,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git cfg80211-mac80211-multi-bssid
head:   851ae31d34063deb1eae49f5d797a12a5557e832
commit: 78ac51f81532c1e361a31ac112c1fea470ea9036 [15/20] mac80211: support multi-bssid
config: i386-randconfig-b0-02090229 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        git checkout 78ac51f81532c1e361a31ac112c1fea470ea9036
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   ERROR: "__umoddi3" [net/wireless/cfg80211.ko] undefined!
>> ERROR: "__umoddi3" [net/mac80211/mac80211.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: 31535 bytes --]

                 reply	other threads:[~2019-02-08 22:04 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=201902090629.X9SzLP26%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@vger.kernel.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).