diff options
author | Andres Salomon <[email protected]> | 2008-07-12 13:47:54 -0700 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2008-07-12 14:33:41 -0700 |
commit | bca5c2c550f16d2dc2d21ffb7b4712bd0a7d32a9 (patch) | |
tree | 5f37f9e04821f71443ca8b6a8d08a0006a1b895e /net/unix/sysctl_net_unix.c | |
parent | 05d81d2222beec7b63ac8c1c8cdb5bb4f82c2bad (diff) |
ov7670: clean up ov7670_read semantics
Cortland Setlow pointed out a bug in ov7670.c where the result from
ov7670_read() was just being checked for !0, rather than <0. This made me
realize that ov7670_read's semantics were rather confusing; it both fills
in 'value' with the result, and returns it. This is goes against general
kernel convention; so rather than fixing callers, let's fix the function.
This makes ov7670_read return <0 in the case of an error, and 0 upon
success. Thus, code like:
res = ov7670_read(...);
if (!res)
goto error;
..will work properly.
Signed-off-by: Cortland Setlow <[email protected]>
Signed-off-by: Andres Salomon <[email protected]>
Acked-by: Jonathan Corbet <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions