From: Simon Horman <horms@verge.net.au>
Date: Wed, 4 Apr 2012 05:06:24 +0000 (+0900)
Subject: datapath: tunnelling: capwap: UDP_ENCAP_CAPWAP is an abitrary value
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7dc05f69efcc3bfc29b8cf5ac74567a940a53c1c;p=openvswitch

datapath: tunnelling: capwap: UDP_ENCAP_CAPWAP is an abitrary value

It seems to me that as the value of UDP_ENCAP_CAPWAP is hardcoded
it would be more appropriate to describe it as arbitrary than
random.

Signed-off-by: Simon Horman <horms@verge.net.au>
Signed-off-by: Jesse Gross <jesse@nicira.com>
---

diff --git a/datapath/vport-capwap.c b/datapath/vport-capwap.c
index 8fbd4a7b..e5b7afb8 100644
--- a/datapath/vport-capwap.c
+++ b/datapath/vport-capwap.c
@@ -361,7 +361,7 @@ static inline struct capwap_net *ovs_get_capwap_net(struct net *net)
 	return &ovs_net->vport_net.capwap;
 }
 
-/* Random value.  Irrelevant as long as it's not 0 since we set the handler. */
+/* Arbitrary value.  Irrelevant as long as it's not 0 since we set the handler. */
 #define UDP_ENCAP_CAPWAP 10
 static int init_socket(struct net *net)
 {