linux-kernel - Re: [ANNOUNCE] linux-staging tree created

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: <20080613143328.GA16506@tuxdriver.com>
Date:	Fri, 13 Jun 2008 10:33:29 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org, linux-next@...r.kernel.org,
	kernel-janitors@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: [ANNOUNCE] linux-staging tree created

On Fri, Jun 13, 2008 at 07:14:32AM -0700, Luis R. Rodriguez wrote:

> This is great. To let this be useful for wireless we'll need
> wireless-testing.git merged as we rely on it for the latest and
> greatest. Is this a possibility?

> We have a few drivers which are not yet ready for
> wireless-testing.git. Airgo is one.
> 
> Anyway, good stuff. Let me know what you think about letting this work
> for wireless too.

I don't think directly pulling wireless-testing is a good idea of
-staging for process-related reasons.  However I think we can arrange
to send something for the new tree.  at76, airgo, and mrv8k are all
decent candidates.

Greg, how does the -staging tree get managed?  Is it periodically
rebuilt (like -next)?  Or would I need to send you pull requests?

John
-- 
John W. Linville
linville@...driver.com
--
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/