On Thu, 2009-04-02 at 20:28 +0200, Johannes Berg wrote: > On Thu, 2009-04-02 at 13:18 -0500, Larry Finger wrote: > > > The problem is the statement #define TRIG_NAME_MAX 50 in include/linux/leds.h. > > When I make it 60, then the trigger file contains "none ide-disk ADP1-online > > BAT0-charging-or-full BAT0-charging BAT0-full phy0rx phy0tx phy0assoc phy0radio > > [rfkill0]" as expected. > > Woah, that's strange. Richard? Larry is seeing problems where, oddly > depending on a patch I have, he's getting garbage for the selected > trigger when reading the trigger sysfs file. > > The trigger's name, should be > led_trigger.name = <something that is NULL> ? : dev_name(&some_dev) > > Does this make any sense to you? No, it doesn't make any sense and the 'fix' he posted isn't valid, just a workaround that happens to help. I suspect there is memory corruption going on somewhere... Cheers, Richard -- Richard Purdie Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
