Comment 16 for bug 413419

Was the kernel patch applied? Can we expect a fix for this issue in a upcoming 2.6.31 kernel update?