[ovs-dev] [PATCH] datapath: tunnelling: capwap: UDP_ENCAP_CAPWAP is an abitrary value

Simon Horman horms at verge.net.au
Wed Apr 4 05:06:24 UTC 2012


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 at verge.net.au>

---

This has been bugging me, sorry for the noise.
---
 datapath/vport-capwap.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/datapath/vport-capwap.c b/datapath/vport-capwap.c
index 8fbd4a7..e5b7afb 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)
 {
-- 
1.7.9.1




More information about the dev mailing list