Searched hist:"2 ebf8c94" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/drivers/misc/mei/ |
| H A D | hbm.c | 2ebf8c94 Mon Sep 16 15:44:43 CDT 2013 Tomas Winkler <tomas.winkler@intel.com> mei: propagate error from write routines instead of ENODEV
ENODEV will cause application to try to reconnect since
it assumes that device went through the reset
write errors are not always fatal it can happen due to
resource contention
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2ebf8c94 Mon Sep 16 15:44:43 CDT 2013 Tomas Winkler <tomas.winkler@intel.com> mei: propagate error from write routines instead of ENODEV
ENODEV will cause application to try to reconnect since
it assumes that device went through the reset
write errors are not always fatal it can happen due to
resource contention
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| H A D | interrupt.c | 2ebf8c94 Mon Sep 16 15:44:43 CDT 2013 Tomas Winkler <tomas.winkler@intel.com> mei: propagate error from write routines instead of ENODEV
ENODEV will cause application to try to reconnect since
it assumes that device went through the reset
write errors are not always fatal it can happen due to
resource contention
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2ebf8c94 Mon Sep 16 15:44:43 CDT 2013 Tomas Winkler <tomas.winkler@intel.com> mei: propagate error from write routines instead of ENODEV
ENODEV will cause application to try to reconnect since
it assumes that device went through the reset
write errors are not always fatal it can happen due to
resource contention
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
| H A D | client.c | 2ebf8c94 Mon Sep 16 15:44:43 CDT 2013 Tomas Winkler <tomas.winkler@intel.com> mei: propagate error from write routines instead of ENODEV
ENODEV will cause application to try to reconnect since
it assumes that device went through the reset
write errors are not always fatal it can happen due to
resource contention
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2ebf8c94 Mon Sep 16 15:44:43 CDT 2013 Tomas Winkler <tomas.winkler@intel.com> mei: propagate error from write routines instead of ENODEV
ENODEV will cause application to try to reconnect since
it assumes that device went through the reset
write errors are not always fatal it can happen due to
resource contention
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|