From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 4/4] net/ieee80211 -> drivers/net/ipw2x00/libipw_* rename
Date: Tue, 11 Nov 2008 23:22:33 +0100 [thread overview]
Message-ID: <200811112322.33623.mb@bu3sch.de> (raw)
In-Reply-To: <1226440265-21240-4-git-send-email-linville@tuxdriver.com>
On Tuesday 11 November 2008 22:51:05 John W. Linville wrote:
> +config LIBIPW
> + tristate
> + select WIRELESS_EXT
> + select CRYPTO
> + select CRYPTO_ARC4
> + select CRYPTO_ECB
> + select CRYPTO_AES
> + select CRYPTO_MICHAEL_MIC
> + select CRYPTO_ECB
> + select CRC32
> + select LIB80211
> + select LIB80211_CRYPT_WEP
> + select LIB80211_CRYPT_TKIP
> + select LIB80211_CRYPT_CCMP
> + ---help---
> + This option enables the hardware independent IEEE 802.11
> + networking stack. This component is deprecated in favor of the
> + mac80211 component.
Let's remove this helptext, or replace it by something that's actually true. ;)
---help---
This option enables common routines for the IPW2100 and IPW2200 drivers.
--
Greetings Michael.
next prev parent reply other threads:[~2008-11-11 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 21:51 [RFC PATCH 1/4] lib80211: absorb crypto bits from net/ieee80211 John W. Linville
2008-11-11 21:51 ` [RFC PATCH 2/4] lib80211: consolidate crypt init routines John W. Linville
2008-11-11 21:51 ` [RFC PATCH 3/4] ipw2x00: relocate ipw2100/ipw2200 to common directory John W. Linville
2008-11-11 21:51 ` [RFC PATCH 4/4] net/ieee80211 -> drivers/net/ipw2x00/libipw_* rename John W. Linville
2008-11-11 22:22 ` Michael Buesch [this message]
2008-11-11 23:21 ` John W. Linville
2008-11-12 3:27 ` Julian Calaby
2008-11-12 10:29 ` Michael Buesch
2008-11-12 10:39 ` Julian Calaby
2008-11-12 16:48 ` [RFC PATCH 1/4] lib80211: absorb crypto bits from net/ieee80211 Harvey Harrison
2008-11-12 18:02 ` John W. Linville
2008-11-12 18:19 ` Harvey Harrison
2008-11-12 18:28 ` John W. Linville
2008-11-12 18:35 ` John W. Linville
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=200811112322.33623.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).