diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-05-27 15:57:31 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-05-27 15:57:31 -0700 |
commit | 5d22fc25d4fc8096d2d7df27ea1893d4e055e764 (patch) | |
tree | 464a86dc3d004dd334e37a8fe7e7b42f8511581e /fs/udf | |
parent | 287980e49ffc0f6d911601e7e352a812ed27768e (diff) | |
download | linux-5d22fc25d4fc8096d2d7df27ea1893d4e055e764.tar.gz linux-5d22fc25d4fc8096d2d7df27ea1893d4e055e764.tar.bz2 linux-5d22fc25d4fc8096d2d7df27ea1893d4e055e764.zip |
mm: remove more IS_ERR_VALUE abuses
The do_brk() and vm_brk() return value was "unsigned long" and returned
the starting address on success, and an error value on failure. The
reasons are entirely historical, and go back to it basically behaving
like the mmap() interface does.
However, nobody actually wanted that interface, and it causes totally
pointless IS_ERR_VALUE() confusion.
What every single caller actually wants is just the simpler integer
return of zero for success and negative error number on failure.
So just convert to that much clearer and more common calling convention,
and get rid of all the IS_ERR_VALUE() uses wrt vm_brk().
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/udf')
0 files changed, 0 insertions, 0 deletions