mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-30 03:27:44 -04:00
Rationalize fasync return values
Most fasync implementations do something like:
return fasync_helper(...);
But fasync_helper() will return a positive value at times - a feature used
in at least one place. Thus, a number of other drivers do:
err = fasync_helper(...);
if (err < 0)
return err;
return 0;
In the interests of consistency and more concise code, it makes sense to
map positive return values onto zero where ->fasync() is called.
Cc: Al Viro <[email protected]>
Signed-off-by: Jonathan Corbet <[email protected]>
This commit is contained in:
parent
76398425bb
commit
60aa49243d
17 changed files with 22 additions and 73 deletions
|
|
@ -1325,11 +1325,7 @@ static int dv1394_fasync(int fd, struct file *file, int on)
|
|||
|
||||
struct video_card *video = file_to_video_card(file);
|
||||
|
||||
int retval = fasync_helper(fd, file, on, &video->fasync);
|
||||
|
||||
if (retval < 0)
|
||||
return retval;
|
||||
return 0;
|
||||
return fasync_helper(fd, file, on, &video->fasync);
|
||||
}
|
||||
|
||||
static ssize_t dv1394_write(struct file *file, const char __user *buffer, size_t count, loff_t *ppos)
|
||||
|
|
|
|||
Loading…
Reference in a new issue