Messages in this thread | | | Subject | Re: [PATCH v4 0/7] Support inhibiting input devices | From | Andrzej Pietrasiewicz <> | Date | Mon, 3 Aug 2020 16:40:58 +0200 |
| |
Hi Dmitry,
W dniu 12.06.2020 o 10:17, Hans de Goede pisze: > Hi, > > On 6/8/20 1:22 PM, Andrzej Pietrasiewicz wrote: >> This is a quick respin of v3, with just two small changes, please see >> the changelog below. >> >> Userspace might want to implement a policy to temporarily disregard input >> from certain devices. >>
<snip>
>> v3..v4: >> - updated the comment in input_open_device() (Hans) >> - used more straightforward locking pattern in adc/exynos (Michał) >> >> v2..v3: >> - ignored autorepeat events in input_get_disposition() if a key is not >> pressed (Hans) >> - dropped inhibit()/uninhibit() driver callbacks (Hans) >> - split ACPI button patch into taking the lock and using the helper (Rafael) >> - dropped the elan_i2c conversion >> - fixed typos in exynos adc >> >> v1..v2: >> - added input_device_enabled() helper and used it in drivers (Dmitry) >> - the fact of open() and close() being called in inhibit/uninhibit paths has >> been emphasized in the commit message of PATCH 6/7 (Dmitry)
<snip>
> > The entire series looks good to me: > > Acked-by: Hans de Goede <hdegoede@redhat.com>
What are the prospects of this series being merged?
Regards,
Andrzej
| |