-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Kevan wrote:
> On Saturday 03 November 2007 07:15:25 am you wrote:
>> It wouldn't be in vanilla 2.6.23, but it would be in the CVS HEAD kernel
>> based on 2.6.23.
>>
>> Today's KOTD kernel[1,2] should have the fix included. This is the tree
>> that will eventually be the update kernel.
>>
>> -Jeff
>>
>> [1] ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH
> 
> 
> Looks good Jeff and yeah I saw that it wasn't in Vanilla 10.3 but never did 
> check out the CVS head. I've also installed 2.6.24RC1 patched from 2.6.23 and 
> well that's clean as expected. 
> 
> When do you think the kernel will get signed off for update? Also, what other 
> fixes may be incorporated with the next release? 

It's in the hands of our maintenance team now, but it should be soon.

The highlights for the fixes for this release are:

* Update to 2.6.22.10
* Fix kernel hang during OCFS2 cluster initialization
* Fix error during OCFS2 disk heartbeat writing
* Fix Oops during natsemi module unload
* Fix machine rebooting instead of power off after shutdown
* Fix for first lid closing not triggering suspend
* Fix for spurious -ENOSPC on reiserfs
* Fix for misplaced unlock in reiserfs_xattr_get() causing process hangs
* Fix for oops in alsa hdsp
* Fix for integer underflow with runt rx frames in 802.11
* Fix an Oops in NFS encode_lookup()
* Improve hda-intel codec probing robustness
* Add suspend/resume support for aic7xxx
* Make scanning of FAT table faster on mount
* Update e1000e to version in 2.6.24-rc1
* Stop zc0301 from claiming Logitech Quickcam
* Load ACPI Bay driver when needed automatically
* Dell CERC support for megaraid_mbox
* Misc Xen fixes

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFHL0EgLPWxlyuTD7IRAojOAJ4oCkblJl84JDwD7XODTItjyC6ewgCggbXz
OcdsXy8MuNqnqdONFBDuZug=
=Obzw
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to