linux-kernel - Re: Slow DOWN, please!!!

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: <4824670A.4000608@garzik.org>
Date:	Fri, 09 May 2008 11:00:26 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>, rjw@...k.pl,
	davem@...emloft.net, linux-kernel@...r.kernel.org,
	jirislaby@...il.com
Subject: Re: Slow DOWN, please!!!

Jiri Kosina wrote:
> On Wed, 30 Apr 2008, Andrew Morton wrote:
> 
>> I get the impression that we're seeing very little non-Stephen testing 
>> of linux-next at this stage.  I hope we can ramp that up a bit, 
>> initially by having core developers doing at least some basic sanity 
>> testing.

I try to test linux-next on a few SATA test boxes, but it's definitely 
not a daily thing.


> Probably it would make sense also for distro vendors to make linux-next 
> snapshosts available in their development distro branches (redhat's 
> rawhide, opensuse's factory, etc), to make it easier to test by those 
> users who are willing to test if it works in their environment, but don't 
> want to compile kernels themselves.

Agreed...  any lead time on linux-next testing would be great.

	Jeff



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