[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO-hwJLQT6Oj2mvDTtQsOHLOTLFeB=_e6ZQZVj2tz92CZUU17A@mail.gmail.com>
Date: Fri, 23 Aug 2019 17:32:24 +0200
From: Benjamin Tissoires <benjamin.tissoires@...hat.com>
To: Filipe Laíns <lains@...hlinux.org>
Cc: Pedro Vanzella <pedro@...rovanzella.com>,
Bastien Nocera <hadess@...ess.net>,
"open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
Jiri Kosina <jikos@...nel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [Resubmit] Read battery voltage from Logitech Gaming mice
On Fri, Aug 23, 2019 at 4:48 PM Filipe Laíns <lains@...hlinux.org> wrote:
>
> On Fri, 2019-08-23 at 16:32 +0200, Benjamin Tissoires wrote:
> > The problem I have with quirks, and that I explained to Filipe on IRC
> > is that this is kernel ABI. Even if there is a very low chance we have
> > someone using this, re-using the same drv_data bit in the future might
> > break someone's device.
>
> But we can reserve those bits. I don't expect there to be a ton of
> devices that need to be quirked, so using the remaining bits should be
> perfectly fine. Do you agree?
Nope. If the code is not ready for upstream, it should not be included.
Cheers,
Benjamin
Powered by blists - more mailing lists