From: "Luis R. Rodriguez" <lrodriguez@atheros•com>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: "linux-wireless@vger•kernel.org" <linux-wireless@vger•kernel.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Re: print_ssid undefined (linux-next 20081103)
Date: Mon, 3 Nov 2008 12:12:06 -0800 [thread overview]
Message-ID: <20081103201206.GB6378@tesla> (raw)
In-Reply-To: <20081103114222.b257f711.randy.dunlap@oracle.com>
On Mon, Nov 03, 2008 at 11:42:22AM -0800, Randy Dunlap wrote:
> Hi,
>
> I'm seeing a few instances of
>
> ERROR: "print_ssid" [drivers/net/wireless/ipw2100.ko] undefined!
>
> with ipw2100 & ipw2200 in today's linux-next (20081103).
>
> These configs have
> # CONFIG_WIRELESS is not set
> CONFIG_WIRELESS_EXT=y
>
> In looking into this more, I see that the wireless drivers can be enabled
> & built even when CONFIG_WIRELESS=n. Is this the expected behavior?
> Seems a bit odd.
Try this.
diff --git a/drivers/net/wireless/Kconfig b/drivers/net/wireless/Kconfig
index 42afaed..6f85bec 100644
--- a/drivers/net/wireless/Kconfig
+++ b/drivers/net/wireless/Kconfig
@@ -125,7 +125,7 @@ config PCMCIA_RAYCS
config IPW2100
tristate "Intel PRO/Wireless 2100 Network Connection"
- depends on PCI && WLAN_80211
+ depends on PCI && WLAN_80211 && LIB80211
select WIRELESS_EXT
select FW_LOADER
select IEEE80211
@@ -183,7 +183,7 @@ config IPW2100_DEBUG
config IPW2200
tristate "Intel PRO/Wireless 2200BG and 2915ABG Network Connection"
- depends on PCI && WLAN_80211
+ depends on PCI && WLAN_80211 && LIB80211
select WIRELESS_EXT
select FW_LOADER
select IEEE80211
next prev parent reply other threads:[~2008-11-03 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 19:42 print_ssid undefined (linux-next 20081103) Randy Dunlap
2008-11-03 20:07 ` Johannes Berg
2008-11-03 20:12 ` Luis R. Rodriguez [this message]
2008-11-03 21:32 ` Randy Dunlap
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=20081103201206.GB6378@tesla \
--to=lrodriguez@atheros$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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