db: fix a type bug
commitbb8b4366ed7ff88b8520deb76f690744cca54246
authorDan Carpenter <dan.carpenter@oracle.com>
Thu, 6 Sep 2018 14:20:36 +0000 (6 17:20 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Thu, 6 Sep 2018 14:20:36 +0000 (6 17:20 +0300)
treecd3195503f806a00ca6990ea976e397e054a8456
parent7f746a2a09a31102c28a2bee81b2c6e0316a29d6
db: fix a type bug

The issue here was there was a function which returned u16 but we had
"ret = -1;".  It turns out the signedness bug doesn't complain if you
return -1 in a u16 function because I guess that's idiomatic.

Anyway, in the DB the type was wrong so it recorded that we were returning
-1 instead of U16_MAX.  So the caller parsed it incorrectly and got
confused.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_db.c