Re: Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

On Fri, Feb 24, 2017 at 5:06 PM, Aniroop Mathur wrote: >> Hi >> >> On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote: >>> On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann >>> wrote: On Thu, Nov 24, 2016 at 9:11 PM,

Re: Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

On Fri, Feb 24, 2017 at 5:06 PM, Aniroop Mathur wrote: >> Hi >> >> On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote: >>> On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann >>> wrote: On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: > continue;

RE: Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

> Hi > > On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote: >> On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann >> wrote: >>> On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur >>> wrote:

RE: Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

> Hi > > On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote: >> On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann >> wrote: >>> On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur >>> wrote: continue; } else if (head != i) {

Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Hi On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote: > On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann wrote: >> On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: >>> continue; >>>

Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Hi On Tue, Jan 31, 2017 at 5:09 PM, Aniroop Mathur wrote: > On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann wrote: >> On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: >>> continue; >>> } else if (head != i) { >>> /* move

RE: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann wrote: > Hi > > On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: >> Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, >> then SYN_DROPPED event is inserted in the event

RE: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann wrote: > Hi > > On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: >> Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, >> then SYN_DROPPED event is inserted in the event queue always. >> >> However, it is not compulsory

RE: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann wrote: > Hi > > On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: >> Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, >> then SYN_DROPPED event is inserted in the event

RE: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

On Sun, Jan 22, 2017 at 6:45 PM, David Herrmann wrote: > Hi > > On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: >> Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, >> then SYN_DROPPED event is inserted in the event queue always. >> >> However, it is not

Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Hi On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: > Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, > then SYN_DROPPED event is inserted in the event queue always. > > However, it is not compulsory that some events are flushed out on every

Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Hi On Thu, Nov 24, 2016 at 9:11 PM, Aniroop Mathur wrote: > Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, > then SYN_DROPPED event is inserted in the event queue always. > > However, it is not compulsory that some events are flushed out on every > EVIOCG[type] ioctl

Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Dear Mr. Dmitry Torokhov, Could you please update about this patch? Thank you. -- Aniroop Mathur On Wed, Dec 14, 2016 at 11:54 PM, Aniroop Mathur wrote: > Hello Mr. Torokhov, > > Would you kindly update about this patch? > Thanks! > > Best Regards, > Aniroop Mathur >

Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Dear Mr. Dmitry Torokhov, Could you please update about this patch? Thank you. -- Aniroop Mathur On Wed, Dec 14, 2016 at 11:54 PM, Aniroop Mathur wrote: > Hello Mr. Torokhov, > > Would you kindly update about this patch? > Thanks! > > Best Regards, > Aniroop Mathur > > > On Fri, Nov 25, 2016

Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Hello Mr. Torokhov, Would you kindly update about this patch? Thanks! Best Regards, Aniroop Mathur On Fri, Nov 25, 2016 at 1:41 AM, Aniroop Mathur wrote: > Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, > then SYN_DROPPED event is inserted in

Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Hello Mr. Torokhov, Would you kindly update about this patch? Thanks! Best Regards, Aniroop Mathur On Fri, Nov 25, 2016 at 1:41 AM, Aniroop Mathur wrote: > Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, > then SYN_DROPPED event is inserted in the event queue always.

[PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, then SYN_DROPPED event is inserted in the event queue always. However, it is not compulsory that some events are flushed out on every EVIOCG[type] ioctl call like in case of empty event queue and in case when EVIOCG[type]

[PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case

Currently, when EVIOCG[type] ioctl call is issued and bits_to_user fails, then SYN_DROPPED event is inserted in the event queue always. However, it is not compulsory that some events are flushed out on every EVIOCG[type] ioctl call like in case of empty event queue and in case when EVIOCG[type]