On Mon, 23 Jul 2012, Matthew Garrett wrote: > On Mon, Jul 16, 2012 at 10:27:57AM +0800, AceLan Kao wrote: > > So, I didn't get the point why we can just remove the event, we don't rely on it > > to enter S3 now, and to take into account that it's deprecated since > > 2007(fb804714), > > I don't think we should do more workaround for this. > > I've no objection to removing the event, I just want to know why we > don't also need a solution in the evdev path. Why is this not a problem > there? Indeed. And if it is related _directly_ to thinkpad-acpi, please state so. Because thinkpad-acpi does have legacy compatibility crap that can issue duplicated events (same event over different paths: evdev, acpi procfs, acpi netlink) but it is supposed to never do that unless actively configured to do so. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
