From 5d0adb24181cda13cab63c863647ec19a7f5dc9f Mon Sep 17 00:00:00 2001 From: Jes Sorensen Date: Wed, 13 May 2015 13:21:58 -0400 Subject: [PATCH] staging: unisys: Remove unused livedump_info Signed-off-by: Jes Sorensen Signed-off-by: Benjamin Romer Signed-off-by: Greg Kroah-Hartman --- drivers/staging/unisys/visorbus/visorchipset.c | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c index 88a2b5e52323..e6d7075ab8fb 100644 --- a/drivers/staging/unisys/visorbus/visorchipset.c +++ b/drivers/staging/unisys/visorbus/visorchipset.c @@ -135,22 +135,6 @@ struct visor_controlvm_payload_info { static struct visor_controlvm_payload_info controlvm_payload_info; -/* Manages the info for a CONTROLVM_DUMP_CAPTURESTATE / - * CONTROLVM_DUMP_GETTEXTDUMP / CONTROLVM_DUMP_COMPLETE conversation. - */ -struct visor_livedump_info { - struct controlvm_message_header dumpcapture_header; - struct controlvm_message_header gettextdump_header; - struct controlvm_message_header dumpcomplete_header; - bool gettextdump_outstanding; - u32 crc32; - unsigned long length; - atomic_t buffers_in_use; - unsigned long destination; -}; - -static struct visor_livedump_info livedump_info; - /* The following globals are used to handle the scenario where we are unable to * offload the payload from a controlvm message due to memory requirements. In * this scenario, we simply stash the controlvm message, then attempt to @@ -2332,8 +2316,6 @@ visorchipset_init(struct acpi_device *acpi_device) memset(&busdev_notifiers, 0, sizeof(busdev_notifiers)); memset(&controlvm_payload_info, 0, sizeof(controlvm_payload_info)); - memset(&livedump_info, 0, sizeof(livedump_info)); - atomic_set(&livedump_info.buffers_in_use, 0); controlvm_channel = visorchannel_create_with_lock(addr, tmp_sz, GFP_KERNEL, uuid); -- 2.39.5