NF_CT_NEW_REPLY definition has been removed upstream as it did not
make sense (NEW can never be a REPLY).
Signed-off-by: Jarno Rajahalme <ja...@ovn.org>
---
datapath/conntrack.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/datapath/conntrack.c b/datapath/conntrack.c
index 13cacf4..4b6fdae 100644
--- a/datapath/conntrack.c
+++ b/datapath/conntrack.c
@@ -81,7 +81,6 @@ static u8 ovs_ct_get_state(enum ip_conntrack_info ctinfo)
switch (ctinfo) {
case IP_CT_ESTABLISHED_REPLY:
case IP_CT_RELATED_REPLY:
- case IP_CT_NEW_REPLY:
ct_state |= OVS_CS_F_REPLY_DIR;
break;
default:
@@ -98,7 +97,6 @@ static u8 ovs_ct_get_state(enum ip_conntrack_info ctinfo)
ct_state |= OVS_CS_F_RELATED;
break;
case IP_CT_NEW:
- case IP_CT_NEW_REPLY:
ct_state |= OVS_CS_F_NEW;
break;
default:
--
2.1.4
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
