datapath-windows: Use OVS_DEFAULT_PORT_NO instead of 0 in a few places

Signed-off-by: Nithin Raju <[email protected]> Signed-off-by: Ben Pfaff <[email protected]> Acked-by: Saurabh Shah <[email protected]>
hugb · Aug 22, 2014 · c5c2c27 · c5c2c27
1 parent 2b829ec
commit c5c2c27
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/datapath-windows/ovsext/OvsActions.c b/datapath-windows/ovsext/OvsActions.c
@@ -271,7 +271,7 @@ OvsDetectTunnelPkt(OvsForwardingContext *ovsFwdCtx,
          * If the packet will not be encapsulated, consume the tunnel context
          * by clearing it.
          */
-        if (ovsFwdCtx->srcVportNo != 0 &&
+        if (ovsFwdCtx->srcVportNo != OVS_DEFAULT_PORT_NO &&
             !OvsIsVifVportNo(ovsFwdCtx->srcVportNo)) {
             ovsFwdCtx->tunKey.dst = 0;
         }

diff --git a/datapath-windows/ovsext/OvsUser.c b/datapath-windows/ovsext/OvsUser.c
@@ -369,7 +369,8 @@ OvsExecuteDpIoctl(PVOID inputBuffer,
         NdisAcquireRWLockRead(gOvsSwitchContext->dispatchLock, &lockState,
                               NDIS_RWL_AT_DISPATCH_LEVEL);
         ndisStatus = OvsActionsExecute(gOvsSwitchContext, NULL, pNbl,
-                                       vport ? vport->portNo : 0,
+                                       vport ? vport->portNo :
+                                               OVS_DEFAULT_PORT_NO,
                                        NDIS_SEND_FLAGS_SWITCH_DESTINATION_GROUP,
                                        &key, NULL, &layers, actions,
                                        execute->actionsLen);