linux-kernel - Re: Staging, place holder for better company/community development model

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:	Mon, 9 Mar 2009 12:41:32 -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 08:21:22AM +0100, Johannes Berg wrote:
> On Sun, 2009-03-08 at 15:33 -0700, Greg KH wrote:
> 
> > > FWIW, I would MUCH prefer if the staging crap never passed any official
> > > mailing lists.
> > 
> > What do you mean by this?  You don't ever want to see any staging
> > patches on any mailing lists?  That doesn't sound helpful.
> 
> 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.

If you don't like this, then just ignore them.

> > I can provide a simple procmail rule if you really don't like this kind
> > of thing, but that seems pretty extreme...
> 
> I can very well filter on my own, thank you; I'm more worried about the
> noise for random third parties who then infer that this is something
> that somebody is working on and that might be useful to work on for
> them.  Neither of that is true for any wireless staging driver, they
> all require complete rewrites that can, imo, use the old code only for
> reference, not for implementation.

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 :)

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/