> It turned out there was no bug in the kernel... ... > It would have been nice if it had made .32 from my first submission, Yeah, the discussion settled down just as the merge window openend, and this isn't high risk, so in retrospect I should have pushed it into 2.6.32. > but now it's fine for .33. It's not stable material. I'll push the documentation update to 2.6.32. I'll push the tweaks to 2.6.33. I don't expec that this will need to be back-ported as only advanced users who also have this BIOS bug will be messing around setting their own custom passive trip point in the first place. thanks, Len Brown, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
