Re: Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

ast event forwarded > by input core to evdev. > > Does the above mentioned points seem okay to you? > > > -- > Best Regards, > Aniroop Mathur > > > - Original Message - > Sender : Dmitry Torokhov <dmitry.torok...@gmail.com> > Date : 2016-

Re: Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

need to insert a SYN_REPORT event or not right after > SYN_DROPPED event using that last consumed event. And I think that it is for > sure that this last event is actually SYN_REPORT event since input core > always send events in packets so SYN_REPORT is always the last event forwarded > b

RE: Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

o you? -- Best Regards, Aniroop Mathur     - Original Message - Sender : Dmitry Torokhov <dmitry.torok...@gmail.com> Date : 2016-11-20 00:30 (GMT+5:30) Title : Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event   Hi Anoroop,   On Wed, Oct 05

RE: Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

-- Best Regards, Aniroop Mathur     - Original Message ----- Sender : Dmitry Torokhov  Date : 2016-11-20 00:30 (GMT+5:30) Title : Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event   Hi Anoroop,   On Wed, Oct 05, 2016 at 12:42:56AM +0530, 

Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hi Anoroop, On Wed, Oct 05, 2016 at 12:42:56AM +0530, Aniroop Mathur wrote: > If last event dropped in the old queue was EV_SYN/SYN_REPORT, then lets > generate EV_SYN/SYN_REPORT immediately after queing EV_SYN/SYN_DROPPED > so that clients would not ignore next valid full packet events. > >

Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hi Anoroop, On Wed, Oct 05, 2016 at 12:42:56AM +0530, Aniroop Mathur wrote: > If last event dropped in the old queue was EV_SYN/SYN_REPORT, then lets > generate EV_SYN/SYN_REPORT immediately after queing EV_SYN/SYN_DROPPED > so that clients would not ignore next valid full packet events. > >

Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hello Mr. Torokhov, As you can see that this patch is pending for a long time, I request you to please review it at the earliest possible. Thanks, Aniroop Mathur On Thu, Oct 13, 2016 at 12:05 AM, Aniroop Mathur wrote: > Hello Mr. Torokhov, > > Hope you are doing

Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hello Mr. Torokhov, As you can see that this patch is pending for a long time, I request you to please review it at the earliest possible. Thanks, Aniroop Mathur On Thu, Oct 13, 2016 at 12:05 AM, Aniroop Mathur wrote: > Hello Mr. Torokhov, > > Hope you are doing great! > > Could you please

Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hello Mr. Torokhov, Hope you are doing great! Could you please help to update about below version of the patch? -- Copying text about last two problems in v8: Problem 1: Handle EVIOCG[type] for queue empty case --> Done Queue empty condition needs to be added before calling

Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

Hello Mr. Torokhov, Hope you are doing great! Could you please help to update about below version of the patch? -- Copying text about last two problems in v8: Problem 1: Handle EVIOCG[type] for queue empty case --> Done Queue empty condition needs to be added before calling

[PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

If last event dropped in the old queue was EV_SYN/SYN_REPORT, then lets generate EV_SYN/SYN_REPORT immediately after queing EV_SYN/SYN_DROPPED so that clients would not ignore next valid full packet events. Signed-off-by: Aniroop Mathur Difference from v8: Added check for

[PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event

If last event dropped in the old queue was EV_SYN/SYN_REPORT, then lets generate EV_SYN/SYN_REPORT immediately after queing EV_SYN/SYN_DROPPED so that clients would not ignore next valid full packet events. Signed-off-by: Aniroop Mathur Difference from v8: Added check for handling EVIOCG[type]