From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wireless-testing: unknown symbol 'wiphy_new'
Date: Thu, 20 Nov 2014 21:02:39 +0100 [thread overview]
Message-ID: <546E48DF.9020908@broadcom.com> (raw)
In-Reply-To: <1416489794.8557.0.camel@sipsolutions.net>
On 11/20/14 14:23, Johannes Berg wrote:
> On Thu, 2014-11-20 at 14:21 +0100, Arend van Spriel wrote:
>> Build a fresh kernel today, ie. 3.18-rc5-wl from wireless-testing and
>> got the following message while building brcmfmac:
>>
>> LD [M] drivers/net/wireless/brcm80211/brcmfmac/brcmfmac.o
>> Building modules, stage 2.
>> MODPOST 2 modules
>> WARNING: "wiphy_new"
>> [drivers/net/wireless/brcm80211/brcmfmac/brcmfmac.ko] undefined!
>>
>> Did not sound encouraging to continue, but did anyway. Not surprisingly
>> the insmod failed. Checking Module.symvers showed:
>>
>> [arend@lb-bun-235 ~/scm/brcm80211-next]
>> $ grep wiphy_new Module.symvers
>> 0xba575a46 wiphy_new_nm net/wireless/cfg80211 EXPORT_SYMBOL
>>
>> Rings a bell? We renamed the file wl_cfg80211.c that does wiphy_new()
>> call to cfg80211.c. Merge issue?
>
> It's probably just a build issue?
>
> wiphy_new() is a static inline pointing to wiphy_new_nm()
Indeed a build issue, but wiphy_new_nm() was recently introduced, right?
Well, actually we were on 3.18-rc1 wireless-testing before I merged today.
Thanks,
Arend
next prev parent reply other threads:[~2014-11-20 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 13:21 wireless-testing: unknown symbol 'wiphy_new' Arend van Spriel
2014-11-20 13:23 ` Johannes Berg
2014-11-20 20:02 ` Arend van Spriel [this message]
2014-11-20 20:09 ` 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=546E48DF.9020908@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).