signed: allow checks like: if (foo < 0 || foo > x) { for unsigned "foo"
commit6e045a185455bdedd34b9a2a07bf9807b6fcaf8f
authorDan Carpenter <dan.carpenter@oracle.com>
Mon, 10 Oct 2011 09:46:04 +0000 (10 12:46 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Mon, 10 Oct 2011 09:46:04 +0000 (10 12:46 +0300)
tree396d9ec704b3ff222130b09a5ae9bf1238fb0bf7
parentae9f54a8a16986223c3f1b888a34ec99b8536a08
signed: allow checks like:  if (foo < 0 || foo > x) { for unsigned "foo"

This silences 48 warnings on my kernel build.  It could do more.  Here are
somethings it still warns about:
   if (foo < 0 || foo > x || something else)
   if (foo > x || foo < 0)
   if ((foo < 0) || (foo > x))

It's the first type of false positive that bothers me the most.  I don't
like when people code in the 2 other styles and handling them seems
tricky...

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