We need this to actually time out, otherwise we can't tell whether we have the
wrong baud rate set. That's fine for a debugger where a human will terminate,
but not for the upcoming inputattach clone.fine for a debugger where a human
will terminate, but not for the upcoming inputattach clone.fine for a debugger
where a human will terminate, but not for the upcoming inputattach clone.fine
for a debugger where a human will terminate, but not for the upcoming
inputattach clone.

Signed-off-by: Peter Hutterer <peter.hutte...@who-t.net>
---
 tools/tools-shared.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/tools/tools-shared.c b/tools/tools-shared.c
index 4d22cdf..2537211 100644
--- a/tools/tools-shared.c
+++ b/tools/tools-shared.c
@@ -164,7 +164,6 @@ int start_tablet(int fd)
 
 int wait_for_tablet(int fd)
 {
-#if 0
        struct pollfd pfd = { fd, POLLIN, 0 };
        int rc;
 
@@ -179,7 +178,6 @@ int wait_for_tablet(int fd)
        } else if (pfd.revents & POLLIN)
                TRACE("data available.\n");
 
-#endif
        return 0;
 }
 
-- 
1.8.5.3


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to