linux-kernel - Linux 2.6.22-rc1

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.98.0705121857100.6739@woody.linux-foundation.org>
Date:	Sat, 12 May 2007 20:20:35 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Linux 2.6.22-rc1

Ok, the merge window has closed, and 2.6.22-rc1 is out there.

The diffstat and shortlogs are way too big to fit under the kernel mailing 
list limits, and the changes are all over the place. Almost seven thousand 
files changed, and that's not double-counting the files that got moved 
around.

Architecture updates, drivers, filesystems, networking, security, build 
scripts, reorganizations, cleanups.. You name it, it's there.

You want a new firewire stack? We've got it. New wireless networking 
infrastructure? Check. New infiniband drivers? Digital video drivers? A 
totally new CPU architecture (blackfin)? Check, check, check.

That said, I think (and certainly hope) that this will not be nearly as 
painful as the big fundamental timer changes for 2.6.21, and while there 
are some pretty core changes there (like the new SLUB allocator, which 
hopefully will end up replacing both SLAB and SLOB), it feels pretty 
solid, and not as scary as ripping the carpet from under the timer 
infrastructure.

So give it a good testing. We'll see how the regression tracking ends up 
working, but in order to actually track that, we want people actively 
testing -rc1 and making good reports!

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