linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "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: Thu, 8 Oct 2009 08:06:15 -0700	[thread overview]
Message-ID: <20091008080615.09c8b803.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1254995282.3713.18.camel@johannes.local>

On Thu, 08 Oct 2009 11:48:02 +0200 Johannes Berg wrote:

> On Wed, 2009-10-07 at 17:12 -0700, Randy Dunlap wrote:
> 
> > > > # CONFIG_WIRELESS is not set
> > > > CONFIG_WIRELESS_EXT=y
> > > > CONFIG_WEXT_SPY=y
> > > > CONFIG_WEXT_PRIV=y
> > > > 
> > > > WEXT_CORE is not enabled.  I haven't found the culprit, but I suspect "select".
> > > 
> > > Interesting.
> > > 
> > > > but what in WIRELESS_EXT would also cause WEXT_CORE to be enabled?
> > > 
> > > Well, the way WEXT_CORE is defined as def_bool y ought to, no?
> > 
> > Ah, I see what you mean.
> > 
> > Here's what's happening:
> > 
> > net/wireless/Kconfig says:
> > 
> > config WEXT_CORE
> > 	def_bool y
> > 	depends on CFG80211_WEXT || WIRELESS_EXT
> > 
> > 
> > and net/Kconfig says:
> > 
> > if WIRELESS
> > 
> > source "net/wireless/Kconfig"
> > source "net/mac80211/Kconfig"
> > 
> > endif # WIRELESS
> > 
> > 
> > so WEXT_CORE actually depends on NET && WIRELESS && (CFG80211_WEXT || WIRELESS_EXT)
> > (that's what xconfig shows me).
> > But WIRELESS is not enabled.  Pooh.
> > 
> > I was already toying with making CONFIG_WIRELESS a real/usable kconfig symbol.
> > That may have to be done unless someone else comes up with another solution.
> 
> Ah!
> 
> It's kinda strange though that you can select wireless drivers without
> selecting WIRELESS. Maybe the solution is as simple as making WLAN
> (drivers/net/wireless/Kconfig) depend on WIRELESS?

Yes, I think that would be a very good start.

---
~Randy

  reply	other threads:[~2009-10-08 15:11 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 [this message]
2009-10-08 18:29                   ` Johannes Berg
2009-10-09 16:06                     ` Randy Dunlap
2009-10-09 16:14                       ` Johannes Berg
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=20091008080615.09c8b803.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).