| commit | 86ea8acc6b494dbadd16a82ed778a68d5b4d4091 | |
| author | David Kershner <david.kershner@unisys.com> | |
| Fri, 12 Jun 2015 20:46:08 +0000 (12 16:46 -0400) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Sat, 13 Jun 2015 00:08:07 +0000 (12 17:08 -0700) | ||
| tree | 3e30d4010a88fa75b3ec7e2024d7b9594b41fa0e | treesnapshot (tar.gz zip) |
| parent | 5e54654c41bfb9216b551fd3a3891c2da60eadae | commitdiff |
staging: unisys: Don't hold device responses until driver loads
Currently if a driver is not loaded for a device, we will not
respond to the device create until it is done. This causes
s-Par to not mark the partition running if the driver for the
device is not loaded. Since there are several devices that
could be assigned to a guest that don't have an actual
driver this will cause us to never go running.
If the device driver is loaded, we WILL continue to only
respond to the device PAUSE message when the device driver
has responded that it is done with the device.
Signed-off-by: David Kershner <david.kershner@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Currently if a driver is not loaded for a device, we will not
respond to the device create until it is done. This causes
s-Par to not mark the partition running if the driver for the
device is not loaded. Since there are several devices that
could be assigned to a guest that don't have an actual
driver this will cause us to never go running.
If the device driver is loaded, we WILL continue to only
respond to the device PAUSE message when the device driver
has responded that it is done with the device.
Signed-off-by: David Kershner <david.kershner@unisys.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| drivers/staging/unisys/visorbus/visorbus_main.c | diffblobblamehistory |