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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 21 Jun 2008 20:02:22 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Greg KH <greg@...ah.com>
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, 2008-06-21 at 10:50 -0700, Greg KH wrote:
> On Sat, Jun 21, 2008 at 03:00:08PM +0200, Peter Zijlstra wrote:
> > 
> > So what motivates people to keep working on items in your tree if
> > distros are already shipping their stuff?
> 
> The fact that the code still isn't upstream?
> 
> And I'm not betting on distros picking this tree up, but it is in an
> easy form if they wish to do so :)

The point was that for some people being carried by distos is upstream
enough.

So I would discourage distros form picking up this tree.

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.

> > Will you drop drivers that stagnate?
> 
> Heh, most of the drivers are in my tree because they were stagnating
> somewhere else :)
> 
> Hopefully no, it's trivial to drag them along forever, but I'll be
> working to get them upstream as fast as I can, and it also provides a
> very nice project for someone to pick up and work on, as a number of
> developers already have.

Good stuff ;-)

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