linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Solomon Peachy <pizza@shaftnet.org>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: ksenija.stanojevic@gmail.com,
	"driverdev-devel@linuxdriverproject.org"
	<driverdev-devel@linuxdriverproject.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Move wlan-ng out of staging?
Date: Fri, 29 Jan 2016 14:24:34 -0500	[thread overview]
Message-ID: <20160129192434.GD5811@shaftnet.org> (raw)
In-Reply-To: <56AB8F18.9000909@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]

On Fri, Jan 29, 2016 at 05:11:04PM +0100, Xose Vazquez Perez wrote:
> >> I'm helping Greg do a bit of cleanup in the staging tree, I noticed that
> >> wlan-ng driver is maybe ready to be moved out of staging. Are there
> >> any TODO tasks left to do beside checkpatch.pl clean-up?
> > 
> > Its FAQ was very clear: ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/FAQ
> > [archived at http://puppylinux.dreamhosters.com/wireless/linux-wlan-org_FAQ.txt ]

As author of that particular FAQ entry (written nearly ten years ago) 
let me say that nothing in there has any bearing on the situation that 
exists today.

At the time, I didn't think it was worth the significant effort to get 
prism2_usb into the mainline, but obviously some enterprising folks 
disagreed with me, and eventually put forth the elbow grease necessary 
to get it into -staging and all of the subsequent cleanups.

From where I sit, the basic question is this: Is the prism2_usb driver 
now considered good enough to promote out of -staging? If not, what 
needs doing and who is willing to see it through?  If it is, then just 
do it already.  :)

Oh, I'm still hosting the firmware files needed for this thing, and I 
see a consistent 4K or so downloads a month.  So there are obviously 
users out there still.

 - Solomon
-- 
Solomon Peachy        		       pizza at shaftnet dot org
Delray Beach, FL                          ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum viditur.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 155 bytes --]

  reply	other threads:[~2016-01-29 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 16:00 Move wlan-ng out of staging? Xose Vazquez Perez
2016-01-29 16:11 ` Xose Vazquez Perez
2016-01-29 19:24   ` Solomon Peachy [this message]
2016-01-29 16:13 ` Sudip Mukherjee
     [not found] <CAL7P5j+iYzpnR+xT013A7AV=bQ8bSn4W1K=qjieFCAiv1YmwRw@mail.gmail.com>
     [not found] ` <20160125181220.GJ5325@mwanda>
2016-01-27 18:27   ` Kalle Valo
2016-01-27 22:48     ` Julian Calaby
2016-01-27 23:07       ` Greg KH
2016-01-27 23:28         ` Julian Calaby
2016-01-27 23:32           ` Greg KH
2016-01-29  0:56             ` Julian Calaby

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=20160129192434.GD5811@shaftnet.org \
    --to=pizza@shaftnet.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=ksenija.stanojevic@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=xose.vazquez@gmail.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).