summaryrefslogtreecommitdiffstats
path: root/drivers/staging/unisys/visorbus/visorchipset.c
diff options
context:
space:
mode:
authorDavid Kershner2015-06-04 15:22:49 +0200
committerGreg Kroah-Hartman2015-06-08 22:36:44 +0200
commit4abce83dca116e2d0b49e1601bff2983e6cf0491 (patch)
tree65f24dc4f67c275f3bafa28e2b156ba8a6b4eaa8 /drivers/staging/unisys/visorbus/visorchipset.c
parentstaging: unisys: Fix clean up path (diff)
downloadkernel-qcow2-linux-4abce83dca116e2d0b49e1601bff2983e6cf0491.tar.gz
kernel-qcow2-linux-4abce83dca116e2d0b49e1601bff2983e6cf0491.tar.xz
kernel-qcow2-linux-4abce83dca116e2d0b49e1601bff2983e6cf0491.zip
staging: unisys: Add the bus device to the visor device list.
When the bus device was created the list_all variables were not being initialized. When the CONTROLVM_BUS_CONFIGURE message was being sent, it was failing to find the bus and produced a panic. Initialize the bus_info->list_all variable by doing a INIT_LIST_HEAD. Signed-off-by: David Kershner <david.kershner@unisys.com> Signed-off-by: Benjamin Romer <benjamin.romer@unisys.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/unisys/visorbus/visorchipset.c')
-rw-r--r--drivers/staging/unisys/visorbus/visorchipset.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c
index 99fa96e80e1e..cf35d9d3a9bc 100644
--- a/drivers/staging/unisys/visorbus/visorchipset.c
+++ b/drivers/staging/unisys/visorbus/visorchipset.c
@@ -1107,6 +1107,7 @@ bus_create(struct controlvm_message *inmsg)
goto cleanup;
}
+ INIT_LIST_HEAD(&bus_info->list_all);
bus_info->chipset_bus_no = bus_no;
bus_info->chipset_dev_no = BUS_ROOT_DEVICE;