From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireless: make WEXT_SPY and WEXT_PRIV select WEXT_CORE
Date: Fri, 09 Oct 2009 18:14:06 +0200 [thread overview]
Message-ID: <1255104846.4095.2.camel@johannes.local> (raw)
In-Reply-To: <20091009090601.73de5dc6.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
On Fri, 2009-10-09 at 09:06 -0700, Randy Dunlap wrote:
> > menuconfig WLAN
> > bool "Wireless LAN"
> > depends on !S390
> > + select WIRELESS
> > default y
> > ---help---
> > This section contains all the pre 802.11 and 802.11 wireless
>
>
> I suppose that's OK, although I prefer "depends" rather than "select".
I tend to as well, but in this case the WIRELESS itself is just an
option that makes other options invisible, it's not used elsewhere, and
as such I think this is ok -- why hide the wireless drivers unless the
user first selects the wireless core options?
OTOH, you already need to select cfg80211/mac80211 for most drivers, so
I suppose "depends on WIRELESS" would be ok too.
> I tracked down one of the problems that I was seeing:
>
> net/wireless/wext-priv.c:206: error: implicit declaration of function 'call_commit_handler'
>
> with:
> # CONFIG_WIRELESS is not set
> CONFIG_WIRELESS_EXT=y
> CONFIG_WEXT_PRIV=y
>
> This is being caused by several drivers in drivers/staging/ doing
> select WEXT_PRIV
> without using either enough dependencies or even more (ugly) selects.
> (or just because kconfig isn't sufficient)
Hah, staging/, well, that's kinda hard to solve I guess. Except by
fixing all the staging/ drivers to depend on WIRELESS too, like the
patch would do for the regular drivers.
I think you can get the same effect now with the non-staging drivers.
I'll submit this patch formally and ask John to include it, and staging/
can just depend on WIRELESS.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-10-09 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091007173517.abfcfa2a.sfr@canb.auug.org.au>
2009-10-07 17:52 ` linux-next: Tree for October 7 (libertas build failure) Randy Dunlap
2009-10-07 18:12 ` Dan Williams
2009-10-07 22:34 ` Johannes Berg
2009-10-07 17:57 ` linux-next: Tree for October 7 (wireless/wext) Randy Dunlap
2009-10-07 21:07 ` [PATCH] wireless: make WEXT_SPY and WEXT_PRIV select WEXT_CORE John W. Linville
2009-10-07 21:55 ` Randy Dunlap
2009-10-07 22:34 ` Johannes Berg
2009-10-07 22:54 ` Randy Dunlap
2009-10-07 23:14 ` Johannes Berg
2009-10-08 0:12 ` Randy Dunlap
2009-10-08 9:48 ` Johannes Berg
2009-10-08 15:06 ` Randy Dunlap
2009-10-08 18:29 ` Johannes Berg
2009-10-09 16:06 ` Randy Dunlap
2009-10-09 16:14 ` Johannes Berg [this message]
2009-10-09 16:32 ` Greg KH
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=1255104846.4095.2.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.com \
--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).