On 11/09/13 10:12, Dmitry Torokhov wrote: > Hi Ryan, > > On Wed, Sep 11, 2013 at 09:32:53AM +1000, Ryan Mallon wrote: >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
