| commit | 10d417a914e5352cddecbdd75ee423c474c35413 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 14 May 2018 11:49:32 +0000 (14 14:49 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 14 May 2018 11:49:32 +0000 (14 14:49 +0300) | ||
| tree | 01ad64f9de3dd4a9fd6f76cf5e02cb5357f9fed6 | treesnapshot (tar.gz zip) |
| parent | 97740b9ecc9d56a6164e4ec6f853d61958de7b17 | commitdiff |
db/fill_db_caller_info.pl: don't perma-ban functions for being called too often
Until recently Smatch would parse uncalled inlines which meant that we
recorded a function call every time those header files were included into
a .c file. That meant that we had a bunch of function which were called a
lot and added to the kernel.common_functions file.
Unfortunately, once they were added they could not be removed.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Until recently Smatch would parse uncalled inlines which meant that we
recorded a function call every time those header files were included into
a .c file. That meant that we had a bunch of function which were called a
lot and added to the kernel.common_functions file.
Unfortunately, once they were added they could not be removed.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_data/db/fill_db_caller_info.pl | diffblobblamehistory |