This is released already.
Lee, it would also help if you could point the address of the patches, or saying where they were sent (with the hash), this can help tracking the issue. Just saying the issue is fixed means nothing from the test perspective.
The patches: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=f20669e439560202e462e896dd1c4a08692e9313 http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=7076754e669ca834346b9915508d6b367a693e56 http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=e2e64dd8604f47bf54693d920c9a6442c8a4c2af http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=96a1b6b70d1bbeac9ca0e1d5caa7b95090e28856
This is released already.
Lee, it would also help if you could point the address of the patches, or saying where they were sent (with the hash), this can help tracking the issue. Just saying the issue is fixed means nothing from the test perspective.
The patches: kernel. ubuntu. com/git? p=ubuntu/ ubuntu- maverick. git;a=commit; h=f20669e439560 202e462e896dd1c 4a08692e9313 kernel. ubuntu. com/git? p=ubuntu/ ubuntu- maverick. git;a=commit; h=7076754e669ca 834346b9915508d 6b367a693e56 kernel. ubuntu. com/git? p=ubuntu/ ubuntu- maverick. git;a=commit; h=e2e64dd8604f4 7bf54693d920c9a 6442c8a4c2af kernel. ubuntu. com/git? p=ubuntu/ ubuntu- maverick. git;a=commit; h=96a1b6b70d1bb eac9ca0e1d5caa7 b95090e28856
http://
http://
http://
http://