From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: [RFC] staging wireless crap: tell people not to work on it
Date: Sun, 22 Mar 2009 10:40:03 +0100 [thread overview]
Message-ID: <1237714803.5100.770.camel@johannes.local> (raw)
Any objections from anyone on this? We've had somebody clean out otus
because he thought it was a good idea...
johannes
---
drivers/staging/at76_usb/TODO | 4 ++--
drivers/staging/otus/TODO | 7 +++----
drivers/staging/rt2860/TODO | 4 ++--
drivers/staging/rt2870/TODO | 9 ++++++++-
drivers/staging/wlan-ng/README | 4 +++-
5 files changed, 18 insertions(+), 10 deletions(-)
--- wireless-testing.orig/drivers/staging/at76_usb/TODO 2009-03-22 10:31:37.000000000 +0100
+++ wireless-testing/drivers/staging/at76_usb/TODO 2009-03-22 10:31:37.000000000 +0100
@@ -1,2 +1,2 @@
-rewrite the driver to use the proper in-kernel wireless stack
-instead of using its own.
+Work on at76c50x-usb instead, possibly using
+this driver as a reference.
--- wireless-testing.orig/drivers/staging/otus/TODO 2009-03-22 10:31:36.000000000 +0100
+++ wireless-testing/drivers/staging/otus/TODO 2009-03-22 10:31:37.000000000 +0100
@@ -1,8 +1,7 @@
TODO:
- - checkpatch.pl cleanups
- - sparse cleanups
- - port to in-kernel 80211 stack
- - proper network developer maintainer
+ Any functionality in this driver should be integrated
+ into the ar9170 driver that is under development on the
+ linux-wireless mailing list.
Please send any patches to Greg Kroah-Hartman <greg@kroah.com> and
Luis Rodriguez <Luis.Rodriguez@Atheros.com> and the
--- wireless-testing.orig/drivers/staging/rt2860/TODO 2009-03-22 10:31:43.000000000 +0100
+++ wireless-testing/drivers/staging/rt2860/TODO 2009-03-22 10:34:12.000000000 +0100
@@ -1,6 +1,6 @@
I'm hesitant to add a TODO file here, as the wireless developers would
really have people help them out on the "clean" rt2860 driver that can
-be found at the rt2860.sf.net site.
+be found at the http://rt2x00.serialmonkey.com/ site.
But, if you wish to clean up this driver instead, here's a short list of
things that need to be done to get it into a more mergable shape:
@@ -8,7 +8,7 @@ things that need to be done to get it in
TODO:
- checkpatch.pl clean
- sparse clean
- - port to in-kernel 80211 stack
+ - port to in-kernel 80211 stack and common rt2x00 infrastructure
- remove reading from /etc/ config files
- review by the wireless developer community
--- wireless-testing.orig/drivers/staging/rt2870/TODO 2009-03-22 10:31:57.000000000 +0100
+++ wireless-testing/drivers/staging/rt2870/TODO 2009-03-22 10:34:04.000000000 +0100
@@ -1,7 +1,14 @@
+I'm hesitant to add a TODO file here, as the wireless developers would
+really have people help them out on the "clean" rt2870 driver that can
+be found at the http://rt2x00.serialmonkey.com/ site.
+
+But, if you wish to clean up this driver instead, here's a short list of
+things that need to be done to get it into a more mergable shape:
+
TODO:
- checkpatch.pl clean
- sparse clean
- - port to in-kernel 80211 stack
+ - port to in-kernel 80211 stack and common rt2x00 infrastructure
- remove reading from /etc/ config files
- review by the wireless developer community
--- wireless-testing.orig/drivers/staging/wlan-ng/README 2009-03-22 10:34:25.000000000 +0100
+++ wireless-testing/drivers/staging/wlan-ng/README 2009-03-22 10:34:32.000000000 +0100
@@ -4,4 +4,6 @@ TODO:
- Lindent cleanups
- move to use the in-kernel wireless stack
-Please send all patches to Greg Kroah-Hartman <greg@kroah.com>
+Please send any patches or complaints about this driver to Greg
+Kroah-Hartman <greg@kroah.com> and don't bother the upstream wireless
+kernel developers about it, they want nothing to do with it.
next reply other threads:[~2009-03-22 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 9:40 Johannes Berg [this message]
2009-03-22 10:33 ` [RFC] staging wireless crap: tell people not to work on it Kalle Valo
2009-03-22 10:39 ` Johannes Berg
2009-03-22 15:51 ` Marcel Holtmann
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=1237714803.5100.770.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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