On Tue, 2017-06-06 at 09:25 +0200, Benjamin Tissoires wrote: > <snip> > Well, as Bastien said, the issue is that old user space is buggy, and > even if we postpone the switch to 4.13, there will always be someone > who > did not updated upower and who will complain. > > As soon as I started the development of this series, Bastien upgraded > upower with the required changes, and usually the development cycle > of > the kernel gives plenty of time for users to upgrade their user space > tools before the kernel hits mainline. > > [...after a little bit of digging...] > > I tried today with a Fedora 25 and the shipped upower that doesn't > have > the bits Bastien worked on last March. Richard should be able to cut a release, UPower hasn't had one since early last year, so it's time in any case :) > I couldn't expose the bug as reported here. The reason being what > Bastien said, there is a "scope" property exported by the kernel > device > which is set to "Device" telling upower to ignore the device > completely > in this version. Unless we added code to the obsolete version of UPower, we don't have a way to tell UPower to not use a particular device as a generic "power_supply" device. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
