Hello Mr. Torokhov,
On Tue, Dec 29, 2015 at 5:11 AM, Dmitry Torokhov
wrote:
> Hi Aniroop,
>
> On Thu, Dec 24, 2015 at 11:25 AM, Aniroop Mathur wrote:
>> The newest event can be SYN_REPORT in case of dropping all old events when
>> buffer is full, but as now there is no device data available to
Hello Mr. Torokhov,
On Tue, Dec 29, 2015 at 5:11 AM, Dmitry Torokhov
wrote:
> Hi Aniroop,
>
> On Thu, Dec 24, 2015 at 11:25 AM, Aniroop Mathur wrote:
>> The newest event can be SYN_REPORT in case of dropping all old events when
>> buffer is full,
Hi Aniroop,
On Thu, Dec 24, 2015 at 11:25 AM, Aniroop Mathur wrote:
> The newest event can be SYN_REPORT in case of dropping all old events when
> buffer is full, but as now there is no device data available to read so
> lets drop SYN_REPORT as well and store only SYN_DROPPED.
>
We can not drop
Hi Aniroop,
On Thu, Dec 24, 2015 at 11:25 AM, Aniroop Mathur wrote:
> The newest event can be SYN_REPORT in case of dropping all old events when
> buffer is full, but as now there is no device data available to read so
> lets drop SYN_REPORT as well and store only
The newest event can be SYN_REPORT in case of dropping all old events when
buffer is full, but as now there is no device data available to read so
lets drop SYN_REPORT as well and store only SYN_DROPPED.
Signed-off-by: Aniroop Mathur
---
drivers/input/evdev.c | 17 +++--
1 file
The newest event can be SYN_REPORT in case of dropping all old events when
buffer is full, but as now there is no device data available to read so
lets drop SYN_REPORT as well and store only SYN_DROPPED.
Signed-off-by: Aniroop Mathur
---
drivers/input/evdev.c | 17
6 matches
Mail list logo