linux-kernel - Re: How linux-staging is released (was Re: linux-staging/linux-next merge/build errors)

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]

Message-ID: <20080621215059.GD15341@kroah.com>
Date:	Sat, 21 Jun 2008 14:50:59 -0700
From:	Greg KH <greg@...ah.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Ingo Molnar <mingo@...e.hu>, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How linux-staging is released (was Re:
	linux-staging/linux-next merge/build errors)

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
--
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/