| 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
| ||
|
Date: Thu, 26 Apr 2007 08:30:01 +0200 From: Jan De Luyck <ml_linuxkernel_20060528@...re.org> To: linux-kernel@...r.kernel.org Subject: Re: Linux 2.6.21 On Thursday 26 April 2007, Linus Torvalds wrote: > If the goal for 2.6.20 was to be a stable release (and it was), the goal > for 2.6.21 is to have just survived the big timer-related changes and some > of the other surprises (just as an example: we were apparently unlucky > enough to hit what looks like a previously unknown hardware errata in one > of the ethernet drivers that got updated etc). > > So it's been over two and a half months, and while it's certainly not the > longest release cycle ever, it still dragged out a bit longer than I'd > have hoped for and it should have. As usual, I'd like to thank Adrian (and > the people who jumped on the entries Adrian had) for keeping everybody on > their toes with the regression list - there's a few entries there still, > but it got to the point where we didn't even know if they were real > regressions, and delaying things further just wasn't going to help. I've just compiled 2.6.21, seems to run fine, in tickless mode, on a Dell D610. Is there any way to check how many timer ticks are firing, except for monitoring /proc/interrupts? Thanks for all the hard work! Jan -- She has an alarm clock and a phone that don't ring -- they applaud. - 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/
Powered by blists - more mailing lists