Re: [PATCH v2] Input: evdev - Add EVIOC mechanism to extract the MTslot state

[Henrik Rydberg]

> However, back in January 2011, Dmitry raised the problem that this
> code was not thread safe.

I had forgotten about that respin, thanks for the reminder.

> What happens if 2 applications ask for
> different slots values (let say X.org and utouch-frame)?

As already pointed out, nothing bad.

[...]
> Asking for the current active slot (of the device) is allowed and
> should be done by every application that starts to talk to evdev.

Right you are. The hunk can be removed at the cost of loss of
symmetry, but then it starts to look really ugly. ;-)

Cheers,
Henrik
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/