Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 14/28] rt2x00: Create rt2x00lib module
Date: Wed, 28 Feb 2007 16:43:13 +0100	[thread overview]
Message-ID: <200702281643.13490.IvDoorn@gmail.com> (raw)
In-Reply-To: <1172677140.5015.22.camel@johannes.berg>

On Wednesday 28 February 2007 16:39, Johannes Berg wrote:
> On Wed, 2007-02-28 at 16:34 +0100, Ivo van Doorn wrote:
> 
> > Nope, in my test it will show up in the menu. The help text has no influence.
> > When the help text is not specified, selecting help on that entry will display
> > "There is no help available for this kernel option." followed by the regular
> > dependency information for that option.
> 
> I think that's only true if other things depend on it as opposed to
> selecting it. I know that cfg80211 used to not show up in Kconfig (and
> that was intentional)

Nothing depended on RT2X00_LIB, I only had the drivers select RT2X00_LIB.
So something has changed or I am missing something. ;)

Ivo

  reply	other threads:[~2007-02-28 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 14:07 [PATCH 14/28] rt2x00: Create rt2x00lib module Ivo van Doorn
2007-02-28 14:50 ` Johannes Berg
2007-02-28 15:12   ` Ivo van Doorn
2007-02-28 15:25     ` Johannes Berg
2007-02-28 15:34       ` Ivo van Doorn
2007-02-28 15:39         ` Johannes Berg
2007-02-28 15:43           ` Ivo van Doorn [this message]
2007-02-28 15:49             ` Johannes Berg
2007-02-28 15:57               ` Ivo van Doorn
2007-02-28 16:00                 ` Johannes Berg
2007-02-28 16:08                   ` Ivo van Doorn
2007-02-28 16:07       ` Holger Schurig
2007-02-28 16:13         ` Johannes Berg

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=200702281643.13490.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --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