From: Johannes Berg <johannes@sipsolutions•net>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: linux-wireless@vger•kernel.org, linux-next@vger•kernel.org,
"John W. Linville" <linville@tuxdriver•com>
Subject: Re: print_ssid undefined (linux-next 20081103)
Date: Mon, 03 Nov 2008 21:07:34 +0100 [thread overview]
Message-ID: <1225742854.3619.64.camel@johannes.berg> (raw)
In-Reply-To: <20081103114222.b257f711.randy.dunlap@oracle.com> (sfid-20081103_204257_052396_C3A3F03F)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Mon, 2008-11-03 at 11:42 -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).
missing lib80211, because those drivers select IEEE80211 which in turns
selects a few things that are then not selected... oh well
> 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.
Yeah, side effect of my patch to hide the IEEE80211 stuff. We may need
to revert that.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-03 20:07 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 [this message]
2008-11-03 20:12 ` Luis R. Rodriguez
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=1225742854.3619.64.camel@johannes.berg \
--to=johannes@sipsolutions$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--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