On Fri, 25 May 2018, Benjamin Tissoires wrote: > When we receive a RMI4 report, we should not unconditionally send an > input_sync event. Instead, we should let the rmi4 transport layer do it > for us. > > This fixes a situation where we might receive X in a report and the rest > in a subsequent one. And this messes up user space. > > Link: https://bugs.freedesktop.org/show_bug.cgi?id=100436 > > Signed-off-by: Benjamin Tissoires <benjamin.tissoires@xxxxxxxxxx> > --- > > Hi, > > Oscar, do you mind if we add your "Tested-by: Oscar Morante <your@email>"? > > Andrew, can you check for any sides effects please? I have now added Oscar's Tested-by: line and queued in for-4.18/rmi. In case any sideeffects are discovered, I'll either not include for-4.18/rmi in the push to Linus, or we'll do incremental fixups on top (depending on the nature of the side-effects :) ). Thanks, -- Jiri Kosina SUSE Labs -- 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
