From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: How linux-staging is released (was Re: linux-staging/linux-next merge/build errors) Date: Sat, 21 Jun 2008 14:50:59 -0700 Message-ID: <20080621215059.GD15341@kroah.com> References: <20080621124017.ec3b0a51.sfr@canb.auug.org.au> <20080621071956.GB2765@kroah.com> <1214053209.3223.220.camel@lappy.programming.kicks-ass.net> <20080621175003.GC14786@kroah.com> <1214071343.3223.249.camel@lappy.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:42393 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752240AbYFUVxL (ORCPT ); Sat, 21 Jun 2008 17:53:11 -0400 Content-Disposition: inline In-Reply-To: <1214071343.3223.249.camel@lappy.programming.kicks-ass.net> Sender: linux-next-owner@vger.kernel.org List-ID: To: Peter Zijlstra Cc: Stephen Rothwell , Ingo Molnar , linux-next@vger.kernel.org, LKML On Sat, Jun 21, 2008 at 08:02:22PM +0200, Peter Zijlstra wrote: > The point was that for some people being carried by distos is upstream > enough. > > So I would discourage distros form picking up this tree. I wouldn't, as some of the drivers work just fine on some arches, but not all, that is why they are not in mainline yet (the network drivers in there right now are an example of this.) > The scenario I was thinking about is some HW vendor writing a shitty > driver, dumping it in your tree - getting picked up by $DISTRO and > saying, job done, people can use it. Leaving you to pick up the pieces - > which, with you not having hw-docs, is a hard job. If this happens, I'll deal with it then :) thanks, greg k-h