aboutsummaryrefslogtreecommitdiff
path: root/drivers/watchdog/ib700wdt.c
diff options
context:
space:
mode:
authorAndres Salomon <dilinger@queued.net>2008-07-12 13:47:54 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-07-12 14:33:41 -0700
commitbca5c2c550f16d2dc2d21ffb7b4712bd0a7d32a9 (patch)
tree5f37f9e04821f71443ca8b6a8d08a0006a1b895e /drivers/watchdog/ib700wdt.c
parent05d81d2222beec7b63ac8c1c8cdb5bb4f82c2bad (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 <csetlow@tower-research.com> Signed-off-by: Andres Salomon <dilinger@debian.org> Acked-by: Jonathan Corbet <corbet@lwn.net> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/watchdog/ib700wdt.c')
0 files changed, 0 insertions, 0 deletions