From: Solomon Peachy <pizza@shaftnet.org>
To: Greg KH <gregkh@linuxfoundation.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: future of prism2_usb (aka wlan-ng) in staging tree
Date: Thu, 7 Nov 2013 11:05:22 -0500 [thread overview]
Message-ID: <20131107160522.GA12612@shaftnet.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Greg, John,
I was wondering what it would take to get the prism2_usb/wlan-ng driver
out of its long home in the staging tree.
It's seen some work over the years, including conversion to cfg80211,
and in general seems to be no worse than its ancient bretheren already
living in net/wireless (ie orinoco and hostap)
There's certianly more internal cleanups that can be performed (eg
collapsing more unnecessary internal APIs such as the MIB handlers) but
at face value it would appears that the TODO items in the README have
been met (other than shutting up checkpatch's style warnings)
I'd be willing to take point on this and make checkpatch happy, but I'm
curious to hear your thoughts on any additional work you think is
necessary to get it out of staging.
Cheers,
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2013-11-07 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 16:05 Solomon Peachy [this message]
[not found] ` <527BC04F.2080000@lwfinger.net>
2013-11-07 16:37 ` future of prism2_usb (aka wlan-ng) in staging tree Solomon Peachy
2013-11-07 17:52 ` John W. Linville
2013-11-07 18:57 ` Solomon Peachy
2013-11-07 19:11 ` John W. Linville
2013-11-07 19:46 ` Solomon Peachy
2013-11-07 22:25 ` Dan Williams
2013-11-07 23:02 ` Solomon Peachy
2013-11-07 23:37 ` Dan Williams
2013-11-08 13:46 ` Solomon Peachy
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=20131107160522.GA12612@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=gregkh@linuxfoundation.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