From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
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:25:38 +0100 [thread overview]
Message-ID: <1172676338.5015.20.camel@johannes.berg> (raw)
In-Reply-To: <200702281612.51383.IvDoorn@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On Wed, 2007-02-28 at 16:12 +0100, Ivo van Doorn wrote:
> Is there any particular reason for RT2X00 to be a config only option?
Not sure, maybe just preference. To me, when going through and not
reading all the config entries, it appears as though rt2x00 is just a
menu but selecting it still means code is built. Maybe there's the
solution too, provide a new menu for all these options, rename RT2X00 to
RT2X00_LIB and hide it by not providing a help text.
> When RT2X00 is a config only option, it would still require RT2X00 to be a
> tristate option.
Good point.
> It would also mean that both RT2X00 and RT2X00_LIB are options the user
> can select (RT2X00_LIB depending on Rt2X00 off course), I can't really see
> the point in that.
No, that's not true, if RT2X00_LIB has no help text it would never show
up to the user.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-02-28 15:26 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 [this message]
2007-02-28 15:34 ` Ivo van Doorn
2007-02-28 15:39 ` Johannes Berg
2007-02-28 15:43 ` Ivo van Doorn
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=1172676338.5015.20.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=ivdoorn@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