oh i see -- i had a conflict b/c i applied this to a branch
which didn't have the recent upstream const patch.
applied.
thanks,
-len
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell servi
this one didn't apply on top of the other two?
On Tue, 3 Jun 2008, Henrique de Moraes Holschuh wrote:
> The less tested codepaths for LED handling, used on ThinkPads 570, 600e/x,
> 770e, 770x, A21e, A2xm/p, T20-22, X20 and maybe a few others, would write
> data to kernel memory it had no business
Rename SW_RADIO to SW_RFKILL_ALL in thinkpad-acpi code and docs, following
5adad0133907790c50283bf03271d920d6897043 "Input: rename SW_RADIO to
SW_RFKILL_ALL".
Signed-off-by: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
---
Documentation/laptops/thinkpad-acpi.txt |2 +-
drivers/misc/thinkpa
Len,
This patchset has my current thinkpad-acpi queue for 2.6.26-rc, rebased
to properly apply to latest Linus. It includes two fixes, one of them
being a regression from 2.6.25 that bites users of older ThinkPads.
Please send them to Linus for mainline merge.
As usual, the patch set is availab
Rework some subdriver init and exit handlers, in order to fix some
initialization error paths that were missing, or broken.
Hitting those bugs should be extremely rare in the real world, but should
that happen, thinkpad-acpi would fail to dealocate some resources and a
reboot might well be needed
The less tested codepaths for LED handling, used on ThinkPads 570, 600e/x,
770e, 770x, A21e, A2xm/p, T20-22, X20 and maybe a few others, would write
data to kernel memory it had no business touching, for leds number 3 and
above. If one is lucky, that illegal write would cause an OOPS, but
chances
