From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"Jayachandran C." <c.jayachandran@gmail.com>,
devel@driverdev.osuosl.org, Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: Is it time to move drivers/staging/netlogic/ out of staging?
Date: Fri, 3 Feb 2017 21:36:09 +0100 [thread overview]
Message-ID: <20170203203609.GA14271@kroah.com> (raw)
In-Reply-To: <1486148236.22276.72.camel@perches.com>
On Fri, Feb 03, 2017 at 10:57:16AM -0800, Joe Perches wrote:
> On Fri, 2017-02-03 at 10:50 -0800, Florian Fainelli wrote:
> > (with JC's other email)
>
> And now with Greg's proper email too
>
> > On 02/03/2017 10:47 AM, Joe Perches wrote:
> > > 64 bit stats isn't implemented, but is that really necessary?
> > > Anything else?
> >
> > Joe, do you have such hardware that you are interested in getting
> > supported, or was that just to reduce the amount of drivers in staging?
> > I am really not clear about what happened to that entire product line,
> > and whether there is any interest in having anything supported these days...
>
> No hardware. Just to reduce staging driver count.
Without hardware or a "real" maintainer, it shouldn't be moved.
Heck, if no one has the hardware, let's just delete the thing.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-03 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 18:47 Is it time to move drivers/staging/netlogic/ out of staging? Joe Perches
2017-02-03 18:50 ` Florian Fainelli
2017-02-03 18:57 ` Joe Perches
2017-02-03 20:36 ` Greg KH [this message]
2017-02-03 20:38 ` Florian Fainelli
2017-02-03 20:44 ` Greg KH
2017-02-04 2:37 ` Florian Fainelli
2017-02-04 8:08 ` Greg KH
2017-02-06 3:21 ` Florian Fainelli
2017-02-06 9:48 ` Greg KH
2017-02-20 11:28 ` Jayachandran C.
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=20170203203609.GA14271@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=c.jayachandran@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=joe@perches.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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