There's some cognitive dissonance when reading "return FALSE"
in a function that returns a pointer (despite FALSE and NULL
being equivalent).

Signed-off-by: Jason Gerecke <killert...@gmail.com>
---
 src/xf86Wacom.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
index 5011fe0..3e128f9 100644
--- a/src/xf86Wacom.c
+++ b/src/xf86Wacom.c
@@ -534,7 +534,7 @@ const char *wcmEventAutoDevProbe (InputInfoPtr pInfo)
        xf86Msg(X_ERROR, "%s: no Wacom event device found (checked %d nodes, 
waited %d msec)\n",
                pInfo->name, i + 1, wait);
        xf86Msg(X_ERROR, "%s: unable to probe device\n", pInfo->name);
-       return FALSE;
+       return NULL;
 }
 
 /*****************************************************************************
-- 
1.7.10.2


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to