On Mon, 27 Mar 2017, Benjamin Tissoires wrote: > From: Bastien Nocera <had...@hadess.net> > > Without a scope defined, UPower assumes that the battery provides > power to the computer it's connected to, like a laptop battery or a UPS. > > Tested-by: Peter Hutterer <peter.hutte...@who-t.net> > Signed-off-by: Bastien Nocera <had...@hadess.net> > Signed-off-by: Benjamin Tissoires <benjamin.tissoi...@redhat.com> > > --- > > no changes in v3 > > changes in v2: > * fixed typo in commit message > --- > drivers/hid/hid-logitech-hidpp.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/drivers/hid/hid-logitech-hidpp.c > b/drivers/hid/hid-logitech-hidpp.c > index 4eeb550..4aaf237 100644 > --- a/drivers/hid/hid-logitech-hidpp.c > +++ b/drivers/hid/hid-logitech-hidpp.c > @@ -761,6 +761,7 @@ static int hidpp20_battery_event(struct hidpp_device > *hidpp, > static enum power_supply_property hidpp_battery_props[] = { > POWER_SUPPLY_PROP_STATUS, > POWER_SUPPLY_PROP_CAPACITY, > + POWER_SUPPLY_PROP_SCOPE,
This certainly assumes some other patchset to be already applied, right? Which tree is this patchset based on, please? Thanks, -- Jiri Kosina SUSE Labs