linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ieee80211: make it depend on drivers that use it
Date: Tue, 14 Oct 2008 16:56:21 -0400	[thread overview]
Message-ID: <20081014205621.GE3349@tuxdriver.com> (raw)
In-Reply-To: <1224008257.3027.2.camel@johannes.berg>

On Tue, Oct 14, 2008 at 08:17:37PM +0200, Johannes Berg wrote:
> On Tue, 2008-10-14 at 13:20 -0400, John W. Linville wrote:
> > Make IEEE80211 depend on IPW2100, IPW2200, or HOSTAP, which all select
> > it.  This removes the need for users to select it manually.
> > 
> > Signed-off-by: John W. Linville <linville@tuxdriver.com>
> > ---
> >  net/ieee80211/Kconfig |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > diff --git a/net/ieee80211/Kconfig b/net/ieee80211/Kconfig
> > index 94ed7d3..44831db 100644
> > --- a/net/ieee80211/Kconfig
> > +++ b/net/ieee80211/Kconfig
> > @@ -1,5 +1,6 @@
> >  config IEEE80211
> >  	tristate "Generic IEEE 802.11 Networking Stack (DEPRECATED)"
> > +	depends on (IPW2100 || IPW2200 || HOSTAP)
> >  	---help---
> >  	This option enables the hardware independent IEEE 802.11
> >  	networking stack.  This component is deprecated in favor of the
> 
> Users will still have to select the crypto options manually I think.

Yes, your patch is better. :-)

-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

      reply	other threads:[~2008-10-14 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 17:20 [PATCH] ieee80211: make it depend on drivers that use it John W. Linville
2008-10-14 18:17 ` Johannes Berg
2008-10-14 20:56   ` John W. Linville [this message]

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=20081014205621.GE3349@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).