linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"Ksenija Stanojević" <ksenija.stanojevic@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"Dan Carpenter" <dan.carpenter@oracle.com>
Subject: Re: Move wlan-ng out of staging?
Date: Wed, 27 Jan 2016 15:32:20 -0800	[thread overview]
Message-ID: <20160127233220.GA28541@kroah.com> (raw)
In-Reply-To: <CAGRGNgU6-saYqZ-LAHjq9cNeptYo8OR-GZQ-66Bv5DDnYi3k5g@mail.gmail.com>

On Thu, Jan 28, 2016 at 10:28:38AM +1100, Julian Calaby wrote:
> Hi Greg,
> 
> On Thu, Jan 28, 2016 at 10:07 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
> >> Hi Glen,
> >>
> >> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo <kvalo@codeaurora.org> wrote:
> >> > Dan Carpenter <dan.carpenter@oracle.com> writes:
> >> >
> >> >> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
> >> >>> Hi All,
> >> >>>
> >> >>> 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?
> >> >
> >> > For questions like this you should CC linux-wireless.
> >> >
> >> >> I happened to look through this code recently.  It's terrible.
> >> >
> >> > And uses wireless extensions, yuck. There's a lot of work to get it into
> >> > reasonable shape, fixing checkpatch warnings will not be enough.
> >>
> >> On the same subject, the wilc1000 driver has taken some pretty big
> >> steps in the past few days, how far away do you think it is from
> >> graduating from staging?
> >
> > I have 221 patches in my to-apply queue to be merged for this driver, at
> > the very least, those need to be merged before anyone should review it
> > for graduation.  That number also implies that there is still quite a
> > lot to be done, but I would not know for sure until that happens.
> 
> I figured that was the case (there's a _lot_ of churn on that driver)
> however I've noticed the patches recently have swung away from being
> straight checkpatch / coding style cleanups towards feature additions
> and bug fixes, hence my question.

Please feel free to audit it and let us know the details :)

  reply	other threads:[~2016-01-27 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL7P5j+iYzpnR+xT013A7AV=bQ8bSn4W1K=qjieFCAiv1YmwRw@mail.gmail.com>
     [not found] ` <20160125181220.GJ5325@mwanda>
2016-01-27 18:27   ` Move wlan-ng out of staging? 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 [this message]
2016-01-29  0:56             ` Julian Calaby
2016-01-29 16:00 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

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=20160127233220.GA28541@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=julian.calaby@gmail.com \
    --cc=ksenija.stanojevic@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).