mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 11:11:45 -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
|
|
@ -184,6 +184,8 @@ static int setfl(int fd, struct file * filp, unsigned long arg)
|
|||
error = filp->f_op->fasync(fd, filp, (arg & FASYNC) != 0);
|
||||
if (error < 0)
|
||||
goto out;
|
||||
if (error > 0)
|
||||
error = 0;
|
||||
}
|
||||
spin_lock(&filp->f_lock);
|
||||
filp->f_flags = (arg & SETFL_MASK) | (filp->f_flags & ~SETFL_MASK);
|
||||
|
|
|
|||
Loading…
Reference in a new issue