linux-kernel - Re: x86 status was Re: -mm merge plans for 2.6.23

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:	Wed, 11 Jul 2007 16:45:11 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Arjan van de Ven <arjan@...radead.org>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: x86 status was Re: -mm merge plans for 2.6.23

On Thu, 12 Jul 2007, Ingo Molnar wrote:
> 
> We also integrated _all_ feedback we got, and we had the capacity and 
> capability to fix whatever other feedback comes back - it just never 
> came ... until today.

One thing I'll happily talk about is that while 2.6.21 was painful, you 
and Thomas in particular were both very responsible about the thing, so 
no, I'm not at all complaining or worried about it in that sense!

I just really _really_ wish we could have two fairly stable releases in a 
row. I think 2.6.22 has the potential to be a pretty good setup, and I'd 
really like to avoid having another 2.6.21 immediately afterwards.

So I'm not worried about integration and getting fixes when things break 
per se, but I *am* worried that this is an area where we've traditionally 
had lots of unexpected problems.

And hey, maybe this time there will be none. I just still smart from the 
last time, so I'd prefer it to go more smoothly this time around.

		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/