| commit | dee007fe8738779c4729c1910646740d91c23c8f | |
| author | Dan Carpenter <error27@gmail.com> | |
| Thu, 5 Mar 2009 13:00:40 +0000 (5 16:00 +0300) | ||
| committer | Dan Carpenter <error27@gmail.com> | |
| Thu, 5 Mar 2009 13:00:40 +0000 (5 16:00 +0300) | ||
| tree | 355c352def2a70bb0785d1ec9b2525baa621e2c3 | treesnapshot (tar.gz zip) |
| parent | 9960f1d777c4d453f2da3239e4eb7b48ca238220 | commitdiff |
Oring the slists seems like merge_slist()
To me it seems like oring the slist is the same as merging he slists.
Both of them take 2 lists and give the union as the result.
Another advantage to merge_slist() is that it sets up the implied pools
correctly.
Signed-off-by: Dan Carpenter <error27@gmail.com>
To me it seems like oring the slist is the same as merging he slists.
Both of them take 2 lists and give the union as the result.
Another advantage to merge_slist() is that it sets up the implied pools
correctly.
Signed-off-by: Dan Carpenter <error27@gmail.com>
| smatch_slist.c | diffblobblamehistory |