From: Jeffrey <jeffrey.br...@unisys.com>
Changed this variable to controlvm_pending_msg
Controlvm_pending_msg => controlvm_pending_msg
Signed-off-by: Jeffrey Brown <jeffrey.br...@unisys.com>
---
drivers/staging/unisys/visorchipset/visorchipset_main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/unisys/visorchipset/visorchipset_main.c
b/drivers/staging/unisys/visorchipset/visorchipset_main.c
index 6536093..30685cb 100644
--- a/drivers/staging/unisys/visorchipset/visorchipset_main.c
+++ b/drivers/staging/unisys/visorchipset/visorchipset_main.c
@@ -136,7 +136,7 @@ static LIVEDUMP_INFO livedump_info;
* this scenario, we simply stash the controlvm message, then attempt to
* process it again the next time controlvm_periodic_work() runs.
*/
-static struct controlvm_message ControlVm_Pending_Msg;
+static struct controlvm_message controlvm_pending_msg;
static BOOL ControlVm_Pending_Msg_Valid = FALSE;
/* Pool of struct putfile_buffer_entry, for keeping track of pending (incoming)
@@ -1999,7 +1999,7 @@ controlvm_periodic_work(struct work_struct *work)
* msg, so try to process it again
* rather than reading a new one
*/
- inmsg = ControlVm_Pending_Msg;
+ inmsg = controlvm_pending_msg;
ControlVm_Pending_Msg_Valid = FALSE;
gotACommand = TRUE;
} else {
@@ -2022,7 +2022,7 @@ controlvm_periodic_work(struct work_struct *work)
* reprocess it on our next loop
*/
handle_command_failed = TRUE;
- ControlVm_Pending_Msg = inmsg;
+ controlvm_pending_msg = inmsg;
ControlVm_Pending_Msg_Valid = TRUE;
}
}
--
1.8.4
_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
