On Tue, 6 Mar 2007 08:44:43 -0800 (PST) Linus Torvalds wrote:
So this one above and  below lose the obvious "negative error"
information, and also prevent such functions from returning a
positive value (> 0), e.g., to indicate a successful amount of
work done (like bytes read or written). The second version above
[1b] also does not quite agree with your statement:
- "negative error values" should preferably always be tested as such
so in the interest of CodingStyle, can you be even clearer?
*** Remember to use Documentation/SubmitChecklist when testing your code ***