staging: unisys: visorbus: Have unisys_vmcall return Linux error instead of VMCALL...
authorDavid Kershner <david.kershner@unisys.com>
Tue, 28 Mar 2017 13:35:01 +0000 (09:35 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 29 Mar 2017 07:17:04 +0000 (09:17 +0200)
commitbd801a0729c3e20f89f3297a5bbf9413339154a7
tree55e908fe5df5fd7de7f2cecc75b5f6e2ee92aa51
parent88845f407cd6d65959e0fb0c224b69b1fbce9604
staging: unisys: visorbus: Have unisys_vmcall return Linux error instead of VMCALL error

The function unisys_vmcall was returning VMCALL specific errors and the
calling code was ignoring which error was actually returned. Instead we
should be mapping the VMCALL error into a proper Linux error and then
returning that, since we now have an error we know what to do with, we
don't have to drop it but we can send it up the stack.

Signed-off-by: David Kershner <david.kershner@unisys.com>
Reviewed-by: Reviewed-by: Tim Sell <timothy.sell@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/unisys/visorbus/visorchipset.c
drivers/staging/unisys/visorbus/vmcallinterface.h