From: Andrew Morton on
On Mon, 26 Oct 2009 08:38:58 +0100
Frans Pop <elendil(a)planet.nl> wrote:

>
> Please consider this patch set for 2.6.32. It was previously submitted
> for 2.6.31, but AFAICT it has not yet been picked up.
>
> All patches have been acked by either Rui or Matthew, with the
> exception of 1/6 and 4/6, but the entire series has been implicitly
> acked by Rui in http://bugzilla.kernel.org/show_bug.cgi?id=13918#c26.
>
> The patch set closes http://bugzilla.kernel.org/show_bug.cgi?id=13918.
>
> Andrew, could you take the set just in case?
>

I'm trying to work out what the actual bug is in here.

afacit some KDE tool put wrong numbers into /proc files, acpi didn't
sanity check them sufficiently and permitted the CPU to overheat, yes?

There seems to be rather a lot of non-bugfix stuff in this patch
series. Perhaps too much for 2.6.32, and a real problem if we want to
backport something into 2.6.31.x and earlier.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Len Brown on
> 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-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/