From 0bbb5aabf794720fa99ae5ea3f55138ded159705 Mon Sep 17 00:00:00 2001
From: Keith Packard <keithp@keithp.com>
Date: Mon, 16 May 2016 21:33:41 -0500
Subject: kdrive: Don't lock input across read in KdNotifyFd

We won't need these locks with the new threaded input code as it holds
the input lock across all of the input device I/O operations.

Signed-off-by: Keith Packard <keithp@keithp.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
---
 hw/kdrive/src/kinput.c | 2 --
 1 file changed, 2 deletions(-)

(limited to 'hw/kdrive')

diff --git a/hw/kdrive/src/kinput.c b/hw/kdrive/src/kinput.c
index 0cf45bbcd..b415a86fe 100644
--- a/hw/kdrive/src/kinput.c
+++ b/hw/kdrive/src/kinput.c
@@ -139,9 +139,7 @@ static void
 KdNotifyFd(int fd, int ready, void *data)
 {
     int i = (int) (intptr_t) data;
-    input_lock();
     (*kdInputFds[i].read)(fd, kdInputFds[i].closure);
-    input_unlock();
 }
 
 static void
-- 
cgit v1.2.3