From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rt2x00: remove experimental on kconfig
Date: Tue, 28 Jul 2009 08:17:50 +0200 [thread overview]
Message-ID: <200907280817.50877.IvDoorn@gmail.com> (raw)
In-Reply-To: <1248736854-443-1-git-send-email-lrodriguez@atheros.com>
On Tuesday 28 July 2009, Luis R. Rodriguez wrote:
> These have been around for a while, if there are issues
> they should be reported.
>
> Cc: Ivo van Doorn <IvDoorn@gmail.com>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
>
> Ivo, is this fair to say? Was surprised to see rt2x00 marked
> as experimental still.
Well I think removing the experimental flag is fine, the most serious
problem with most drivers is the throughput, but I guess that is not
a blocker for removing the experimental flag.
However please move the experimental flag to rt2800usb, since that
driver is very recent and is not working correctly for a lot of people.
Thanks,
Ivo
> drivers/net/wireless/rt2x00/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/Kconfig b/drivers/net/wireless/rt2x00/Kconfig
> index f970aa2..379da5c 100644
> --- a/drivers/net/wireless/rt2x00/Kconfig
> +++ b/drivers/net/wireless/rt2x00/Kconfig
> @@ -1,8 +1,8 @@
> menuconfig RT2X00
> tristate "Ralink driver support"
> - depends on MAC80211 && WLAN_80211 && EXPERIMENTAL
> + depends on MAC80211 && WLAN_80211
> ---help---
> - This will enable the experimental support for the Ralink drivers,
> + This will enable the support for the Ralink drivers,
> developed in the rt2x00 project <http://rt2x00.serialmonkey.com>.
>
> These drivers make use of the mac80211 stack.
prev parent reply other threads:[~2009-07-28 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 23:20 [PATCH] rt2x00: remove experimental on kconfig Luis R. Rodriguez
2009-07-28 6:17 ` Ivo van Doorn [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=200907280817.50877.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).