Rafael J. Wysocki writes: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.26 and 2.6.27. > > The following bug entry is on the current list of known regressions > introduced between 2.6.26 and 2.6.27. Please verify if it still should > be listed and let me know (either way). The commit that introduced the problem went into Linus' tree after 2.6.27, so it's not a regression from 2.6.26. In other words, 2.6.27 doesn't have the problem. It's a firmware bug in some old firmware versions that got triggered by the kernel change, not a kernel bug per se. The commit has been reverted in Linus' tree now, so there isn't a regression from 2.6.27 any more. Paul. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
