Removed the check for previous dump state before calling FreeUserDumpState
as the check is also performed in the latter function.
Signed-off-by: Sorin Vinturis <svintu...@cloudbasesolutions.com>
---
datapath-windows/ovsext/Datapath.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/datapath-windows/ovsext/Datapath.c
b/datapath-windows/ovsext/Datapath.c
index 1b504a2..1ba96f2 100644
--- a/datapath-windows/ovsext/Datapath.c
+++ b/datapath-windows/ovsext/Datapath.c
@@ -774,7 +774,7 @@ OvsDeviceControl(PDEVICE_OBJECT deviceObject,
* state in the instance to indicate the command that started the dump
* operation. The state can setup 'ovsMsgReadOp' appropriately. Note
* that 'ovsMsgReadOp' is needed only in this function to call into the
- * appropraite handler. The handler itself can access the state in the
+ * appropriate handler. The handler itself can access the state in the
* instance.
*
* In the absence of a dump start, return 0 bytes.
@@ -1344,9 +1344,7 @@ OvsSetupDumpStart(POVS_USER_PARAMS_CONTEXT usrParamsCtx)
* This operation should be setting up the dump state. If there's any
* previous state, clear it up so as to set it up afresh.
*/
- if (instance->dumpState.ovsMsg != NULL) {
- FreeUserDumpState(instance);
- }
+ FreeUserDumpState(instance);
return InitUserDumpState(instance, msgIn);
}
--
1.9.0.msysgit.0
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
