6 Jan
2015
6 Jan
'15
3:42 a.m.
On 6 January 2015 at 05:22, Rafael J. Wysocki rjw@rjwysocki.net wrote:
Now note how much useful the above is than the stuff in your original changelog.
Yes, its all in logs now :)
I'd say all depends on whether or not the callers deal with the error code appropriately. If it is propagated all the way to user space, it really should *not* be -EBUSY, but otherwise this is a matter of how the callers handle the given error code.
It might not get propagated to user space for now, but not sure if that wouldn't change in future. Even if it stays only within the kernel, we better return the error codes that fit the best for a particular situation and so I would still like to get this through.