From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
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 21:43:26 +0530 [thread overview]
Message-ID: <20160129161326.GA15484@sudip-laptop> (raw)
In-Reply-To: <56AB8C90.2050909@gmail.com>
On Fri, Jan 29, 2016 at 05:00:16PM +0100, Xose Vazquez Perez wrote:
> Ksenija 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 ]
>
> --cut--
> Q: When will linux-wlan-ng be merged into the mainline kernel?
>
> Short answer: Never.
The ultimate aim of a driver in staging is to graduate out of staging
area into the main part of the kernel. If it is already known that this
driver can never move out of staging then IMHO its better to remove it.
regards
sudip
next prev parent reply other threads:[~2016-01-29 16:13 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
2016-01-29 16:13 ` Sudip Mukherjee [this message]
[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=20160129161326.GA15484@sudip-laptop \
--to=sudipm.mukherjee@gmail.com \
--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