| commit | 7a34efff0cfbeffe36df521248fe3e3a1ee08b3c | |
| author | Dan Carpenter <error27@gmail.com> | |
| Wed, 30 Dec 2009 08:52:41 +0000 (30 10:52 +0200) | ||
| committer | Dan Carpenter <error27@gmail.com> | |
| Wed, 30 Dec 2009 08:52:41 +0000 (30 10:52 +0200) | ||
| tree | 6353415e2c5e866d9a1e2c84568f9a8459cd64a9 | treesnapshot (tar.gz zip) |
| parent | 526801a80aebe368a3863172dd679c65aa6e5398 | commitdiff |
dma_on_stack: &foo means it's an error too
Mostly this situation is caused by:
int foo;
usb_control_msg(..., &foo, ...);
It does cause some false positives as well when people do:
usb_control_msg(..., &bar[1], ...);
But in my testing those are rare, and most times should be
cleaned up anyway.
Signed-off-by: Dan Carpenter <error27@gmail.com>
Mostly this situation is caused by:
int foo;
usb_control_msg(..., &foo, ...);
It does cause some false positives as well when people do:
usb_control_msg(..., &bar[1], ...);
But in my testing those are rare, and most times should be
cleaned up anyway.
Signed-off-by: Dan Carpenter <error27@gmail.com>
| check_dma_on_stack.c | diffblobblamehistory |