linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "Julian Calaby" <julian.calaby@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 4/4] net/ieee80211 -> drivers/net/ipw2x00/libipw_* rename
Date: Wed, 12 Nov 2008 11:29:42 +0100	[thread overview]
Message-ID: <200811121129.43125.mb@bu3sch.de> (raw)
In-Reply-To: <646765f40811111927y7e25bca1xb2bdb7e2b4db112a@mail.gmail.com>

On Wednesday 12 November 2008 04:27:58 Julian Calaby wrote:
> On Wed, Nov 12, 2008 at 10:21, John W. Linville <linville@tuxdriver.com> wrote:
> > On Tue, Nov 11, 2008 at 11:22:33PM +0100, Michael Buesch wrote:
> >> 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.
> >
> > Yes, good comment.
> 
> Does this option even need to be visible?
> 
> Only the ipw2x00 drivers use it - and they select it - so do we need
> to bother the user with it?

That's how it currently works in the patch.
The help text is only there for the reader of the Kconfig file. It won't
show up in menuconfig or whatever.

-- 
Greetings Michael.

  reply	other threads:[~2008-11-12 10:30 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
2008-11-11 23:21         ` John W. Linville
2008-11-12  3:27           ` Julian Calaby
2008-11-12 10:29             ` Michael Buesch [this message]
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=200811121129.43125.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=julian.calaby@gmail.com \
    --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).