| commit | 88c8a51acf5ef70e6939e88d9bd46fb56c75d3ef | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 28 Oct 2014 10:21:24 +0000 (28 13:21 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 28 Oct 2014 10:21:24 +0000 (28 13:21 +0300) | ||
| tree | 112ddb4481bb3f4ee699bf1a634637189405cc45 | treesnapshot (tar.gz zip) |
| parent | 90ae5d455baaf674aa985e0e42a0adfb05165095 | commitdiff |
free: don't turn off warnings if --spammy is set
This change could mean that there are duplicate warnings when the --spammy
flag is used but that's ok. In the original code, we could miss certain
types of bugs when the --spammy flag was used and that's not ok.
Also past experience says that it's a bad idea to turn off any warnings
when --spammy is used because I always run with --spammy on and might not
see false positives.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
This change could mean that there are duplicate warnings when the --spammy
flag is used but that's ok. In the original code, we could miss certain
types of bugs when the --spammy flag was used and that's not ok.
Also past experience says that it's a bad idea to turn off any warnings
when --spammy is used because I always run with --spammy on and might not
see false positives.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| check_free.c | diffblobblamehistory |