netdev - Re: Future of the Wimedia LLC Protocol (WLP) subsystem/drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20101028.092943.193715325.davem@davemloft.net>
Date:	Thu, 28 Oct 2010 09:29:43 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	greg@...ah.com
Cc:	randy.dunlap@...cle.com, david.vrabel@....com,
	netdev@...r.kernel.org
Subject: Re: Future of the Wimedia LLC Protocol (WLP) subsystem/drivers

From: Greg KH <greg@...ah.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html