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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Mar 2009 22:00:18 -0700
From:	Greg KH <greg@...ah.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	"Luis R. Rodriguez" <mcgrof@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jouni Malinen <j@...fi>, Sujith <m.sujith@...il.com>,
	Sujith <Sujith.Manoharan@...eros.com>,
	Senthilkumar Balasubramanian 
	<Senthilkumar.Balasubramanian@...eros.com>,
	"John W. Linville" <linville@...driver.com>,
	Christoph Hellwig <hch@...radead.org>,
	Vasanthakumar Thiagarajan <vasanth@...eros.com>
Subject: Re: Staging, place holder for better company/community development
	model

On Mon, Mar 09, 2009 at 10:20:33PM +0100, Johannes Berg wrote:
> On Mon, 2009-03-09 at 12:41 -0700, Greg KH wrote:
> 
> > > Staging drivers will typically be an extremely huge amount of crap that
> > > just floods mailing lists. I don't care about those I don't read, but I
> > > would prefer to not have wireless staging drivers cross the wireless
> > > list which makes it seem like somebody is actually interested in those
> > > drivers.
> > 
> > I was asked by the wireless maintainer and some of the wireless
> > developers to send such patches to the list, so that everyone knows
> > exactly what is going on in the staging tree.
> 
> This is a misrepresentation, a number of people have asked for this on
> specific drivers they are actively working on and that already are in
> usable shape.

Ok, so I'll be glad to not cc: the linux-wireless list if the maintainer
asks me to.

> > That's not true, some of them are being reworked as you type, to be a
> > "real" wireless driver eventually.
> > 
> > Incremental development over time is sometimes a good thing, instead of
> > total rewrites :)
> 
> Except it doesn't work for most of the wireless drivers you've sucked in
> without asking any wireless developers whether that makes any sense or
> not.

Any specific examples?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ