user_data: use the new return_states database table
commit15199510a7e1450d0d39cd9e73f019e31b2da74d
authorDan Carpenter <dan.carpenter@oracle.com>
Tue, 14 Aug 2012 07:57:11 +0000 (14 10:57 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Tue, 14 Aug 2012 07:57:11 +0000 (14 10:57 +0300)
treeaf64cf867895669af5d61e53748ee898dcfaf4ee
parent859a28767926e9ff8f62f0cc76976eb6d1e52d47
user_data: use the new return_states database table

In the old code only variables could be user data.  Call assignments were
handled as a special case where they would set the variable to user data.
In the new code, is_user_data() looks up the function in the data base.

Also the new code uses a different table than before.  That doesn't make
a difference but I didn't want to have duplicative tables.

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