From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751396AbdFBNrN (ORCPT ); Fri, 2 Jun 2017 09:47:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28851 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130AbdFBNrL (ORCPT ); Fri, 2 Jun 2017 09:47:11 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 501A6C0587CA Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=benjamin.tissoires@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 501A6C0587CA Date: Fri, 2 Jun 2017 15:47:03 +0200 From: Benjamin Tissoires To: Bastien Nocera Cc: Dave Hansen , Jiri Kosina , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp Message-ID: <20170602134702.GQ1293@mail.corp.redhat.com> References: <20170327145939.29824-1-benjamin.tissoires@redhat.com> <0cdc8dda-de3f-c3d0-07da-65612860a70f@intel.com> <1496345185.2570.3.camel@hadess.net> <20170602072907.GK1293@mail.corp.redhat.com> <1496408048.2570.11.camel@hadess.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1496408048.2570.11.camel@hadess.net> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Fri, 02 Jun 2017 13:47:11 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Jun 02 2017 or thereabouts, Bastien Nocera wrote: > On Fri, 2017-06-02 at 09:29 +0200, Benjamin Tissoires wrote: > > > > > Bastien, is is possible to have a simple udev rule that tells upower > > to > > ignore the battery device if builtin_power_supply is there? > > That way we can tell people running old upower to use this to be sure > > to > > ignore the kernel device and just rely on the upower hidpp support? > > I'm not sure where we'd ship that in a way that would make it work > differently based on the version of UPower. In UPower? Well, UPower > 0.99.x is the stable track for UPower, and the git master already has > support for this feature. > > I'm not sure what else would need to be done. I was more thinking at a snippet that we drop on this mailing list (here) that users can carefully copy/paste in their /etc and remove themself once they upgrade the system. Though OTOH, that's relying on users remembering that they have a special conf that need to be removed in a later update. Cheers, Benjamin