mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Luca Coelho <luciano.coelho@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Kalle Valo <kvalo@codeaurora.org>
Subject: ld: drivers/net/wireless/intel/iwlwifi/iwl-devtrace.h:81: undefined reference to `ieee80211_hdrlen'
Date: Fri, 18 Jan 2019 03:52:53 +0800	[thread overview]
Message-ID: <201901180349.Fq6xzBcd%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   47bfa6d9dc8c060bf56554a465c9031e286d2f80
commit: aca432f06b8a60a92b27fb46e6518a19b28ca93f iwlwifi: make MVM and DVM depend on MAC80211
date:   4 weeks ago
config: x86_64-randconfig-g3-201902 (attached as .config)
compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
reproduce:
        git checkout aca432f06b8a60a92b27fb46e6518a19b28ca93f
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   ld: drivers/net/wireless/intel/iwlwifi/iwl-eeprom-parse.o: in function `iwl_init_channel_map':
   drivers/net/wireless/intel/iwlwifi/iwl-eeprom-parse.c:609: undefined reference to `ieee80211_channel_to_frequency'
   ld: drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.o: in function `iwl_init_channel_map':
   drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c:353: undefined reference to `ieee80211_channel_to_frequency'
   ld: drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.o: in function `iwl_parse_nvm_mcc_info':
   drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c:1050: undefined reference to `ieee80211_channel_to_frequency'
   ld: drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c:1099: undefined reference to `reg_query_regdb_wmm'
   ld: drivers/net/wireless/intel/iwlwifi/pcie/tx.o: in function `iwl_trans_pcie_tx':
   drivers/net/wireless/intel/iwlwifi/pcie/tx.c:2317: undefined reference to `ieee80211_hdrlen'
   ld: drivers/net/wireless/intel/iwlwifi/pcie/tx-gen2.o: in function `iwl_pcie_gen2_build_tfd':
   drivers/net/wireless/intel/iwlwifi/pcie/tx-gen2.c:550: undefined reference to `ieee80211_hdrlen'
   ld: drivers/net/wireless/intel/iwlwifi/iwl-devtrace.o: in function `iwl_rx_trace_len':
   drivers/net/wireless/intel/iwlwifi/iwl-devtrace.h:81: undefined reference to `ieee80211_hdrlen'
>> ld: drivers/net/wireless/intel/iwlwifi/iwl-devtrace.h:81: undefined reference to `ieee80211_hdrlen'
>> ld: drivers/net/wireless/intel/iwlwifi/iwl-devtrace.h:81: undefined reference to `ieee80211_hdrlen'
   ld: drivers/net/wireless/intel/iwlwifi/iwl-devtrace.o:drivers/net/wireless/intel/iwlwifi/iwl-devtrace.h:81: more undefined references to `ieee80211_hdrlen' follow

---
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: 34818 bytes --]

             reply	other threads:[~2019-01-17 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 19:52 kbuild test robot [this message]
2019-01-18  4:44 ` Kalle Valo

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=201901180349.Fq6xzBcd%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luciano.coelho@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

all inboxes | Powered by JetHome®