From: Kalle Valo <kvalo@codeaurora.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxwifi <linuxwifi@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Luca Coelho <luciano.coelho@intel.com>
Subject: Re: linux-next: Tree for Jan 10 (iwlwifi)
Date: Fri, 11 Jan 2019 13:51:47 +0200 [thread overview]
Message-ID: <87pnt35s4s.fsf@purkki.adurom.net> (raw)
In-Reply-To: <2069197c-c758-6c4e-d30c-3f6baa10b841@infradead.org> (Randy Dunlap's message of "Thu, 10 Jan 2019 13:41:33 -0800")
Randy Dunlap <rdunlap@infradead.org> writes:
> On 1/9/19 8:14 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20190109:
>>
>
> on x86_64:
>
> WARNING: unmet direct dependencies detected for MAC80211_LEDS
> Depends on [n]: NET [=y] && WIRELESS [=y] && MAC80211 [=n] && LEDS_CLASS [=y]
> Selected by [y]:
> - IWLWIFI_LEDS [=y] && NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_INTEL [=y] && IWLWIFI [=y] && (LEDS_CLASS [=y]=y || LEDS_CLASS [=y]=IWLWIFI [=y])
>
> and then
>
> ld: drivers/net/wireless/intel/iwlwifi/iwl-eeprom-parse.o: in function `iwl_parse_eeprom_data':
> iwl-eeprom-parse.c:(.text+0x7c4): undefined reference to `ieee80211_channel_to_frequency'
> ld: drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.o: in function `iwl_init_sbands':
> iwl-nvm-parse.c:(.text+0x37f): undefined reference to `ieee80211_channel_to_frequency'
> ld: drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.o: in function `iwl_parse_nvm_mcc_info':
> iwl-nvm-parse.c:(.text+0xce9): undefined reference to `ieee80211_channel_to_frequency'
> ld: iwl-nvm-parse.c:(.text+0xe9b): undefined reference to `reg_query_regdb_wmm'
> ld: drivers/net/wireless/intel/iwlwifi/pcie/tx.o: in function `iwl_trans_pcie_tx':
> tx.c:(.text+0x344d): undefined reference to `ieee80211_hdrlen'
> ld: drivers/net/wireless/intel/iwlwifi/pcie/tx-gen2.o: in function `iwl_trans_pcie_gen2_tx':
> tx-gen2.c:(.text+0xd93): undefined reference to `ieee80211_hdrlen'
> ld: drivers/net/wireless/intel/iwlwifi/iwl-devtrace.o: in function `iwl_rx_trace_len':
> iwl-devtrace.c:(.text+0x974): undefined reference to `ieee80211_hdrlen'
Kbuild bot also reported this and Luca (CCed) is working on a fix.
Thanks for the report.
--
Kalle Valo
prev parent reply other threads:[~2019-01-11 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190110151409.7d0916c8@canb.auug.org.au>
2019-01-10 21:41 ` linux-next: Tree for Jan 10 (iwlwifi) Randy Dunlap
2019-01-11 11:51 ` Kalle Valo [this message]
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=87pnt35s4s.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).