linux-kernel - Re: Possibility for an external staging tree

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:	Thu, 28 Mar 2013 15:53:00 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	Adrian Chadd <adrian@...ebsd.org>, Jouni Malinen <j@...fi>,
	Kalle Valo <kvalo@...rom.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kathy Giori <Kathy.Giori@....qualcomm.com>,
	Yanbo Li <dreamfly281@...il.com>,
	Mathieu Olivari <mathieu@....qualcomm.com>,
	k.eugene.e@...il.com
Subject: Re: Possibility for an external staging tree - bring up quality code

On Thu, Mar 28, 2013 at 01:13:23PM -0700, Luis R. Rodriguez wrote:

<huge snip>

> This has me thinking if it makes sense to have an external driver tree
> for staging drivers but lead by engineers who already know the rules
> of upstream, they just want to get things done faster.

That's called a "fork" or "tree" or whatever you want to call it, and
all of us have them, and end up merging stuff to mainline through them
eventually.

There is no need to "codify" something that we all have been doing for
years.  If someone thinks they can "work faster" in their own tree,
great for them, have them do it.  I don't see what I need to agree or
disagree with here to keep anyone from doing such a thing.

Or am I just totally missing something here?

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/