[PATCH 1/2] uinput: Support injecting multiple events in one write() call · Ryan Mallon <hidden> · 2013-09-10
[PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event · Ryan Mallon <hidden> · 2013-09-10
Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event · Dmitry Torokhov <dmitry.torokhov@gmail.com> · 2013-09-11
Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event · Ryan Mallon <hidden> · 2013-09-11
Re: [PATCH 1/2] uinput: Support injecting multiple events in one write() call · Dmitry Torokhov <dmitry.torokhov@gmail.com> · 2013-09-11
Re: [PATCH 1/2] uinput: Support injecting multiple events in one write() call · Ryan Mallon <hidden> · 2013-09-11

Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event

From: Ryan Mallon <hidden>
Date: 2013-09-11 00:26:16
Also in: lkml

On 11/09/13 10:12, Dmitry Torokhov wrote:

Hi Ryan,

On Wed, Sep 11, 2013 at 09:32:53AM +1000, Ryan Mallon wrote:

quoted

Call input_inject_event rather than input_event in uinput_inject_event. This
mirrors the behaviour of evdev_write. input_inject_event will ignore the
injected event if the uinput input device has been grabbed for exclusive
access by a handler other than uinput.

uinput is not an input handler but input driver and therefore should
continue using input_event().

Ah, I wasn't sure about this, which is why I broke it out into a
separate patch. Sorry for the noise.

~Ryan

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help