From: David Miller <davem@davemloft.net>
To: greg@kroah.com
Cc: randy.dunlap@oracle.com, david.vrabel@csr.com, netdev@vger.kernel.org
Subject: Re: Future of the Wimedia LLC Protocol (WLP) subsystem/drivers
Date: Thu, 28 Oct 2010 09:29:43 -0700 (PDT) [thread overview]
Message-ID: <20101028.092943.193715325.davem@davemloft.net> (raw)
In-Reply-To: <20101020192233.GA8912@kroah.com>
From: Greg KH <greg@kroah.com>
Date: Wed, 20 Oct 2010 12:22:33 -0700
> On Wed, Oct 20, 2010 at 09:15:41AM -0700, Randy Dunlap wrote:
>> On Tue, 19 Oct 2010 17:30:47 +0100 David Vrabel wrote:
>>
>> > Hi,
>> >
>> > I've have been nominally the maintainer of the Wimedia LLC Protocol
>> > (WLP) subsystem and driver since it was originally submitted. I am no
>> > longer in a position to even pretend to be a maintainer.
>> >
>> > The only usable hardware was an Intel i1480 devices with beta firmware
>> > that was never released as a product. Intel have since sold all there
>> > UWB/WLP IP and I see little prospect of there ever being hardware
>> > commercially available for WLP.
>> >
>> > Here are a number of options:
>> >
>> > 1. Someone else maintains it. Any volunteers?
>> >
>> > 2. It gets labelled as Orphaned in MAINTAINERS.
>> >
>> > 3. It gets moved to staging.
>> >
>> > 4, It gets removed.
>> >
>> > If no one says anything I'll submit a patch to Linus to mark it as Orphaned.
>>
>> I'd say either 3 or 4.
>>
>> It could go to staging on it way to removal, but that's not really necessary.
>>
>>
>> cc: gregkh
>
> 3 or 4 is fine with me, which ever David wants.
I'm fine with either but prefer 4, if we want to resurrect the code
for whatever reason it is there in the history and we can just revert
the revert commit to get it all back.
prev parent reply other threads:[~2010-10-28 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 16:30 Future of the Wimedia LLC Protocol (WLP) subsystem/drivers David Vrabel
2010-10-20 16:15 ` Randy Dunlap
2010-10-20 19:22 ` Greg KH
2010-10-28 16:29 ` David Miller [this message]
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=20101028.092943.193715325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.vrabel@csr.com \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.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).