Remove client_index field from replies in API

- replies should not need to contain client_index since
  it is used to identify sender of requests to VPP

Change-Id: Iece3853b3f020054ee1652b149d0cf8d9580db4e
Signed-off-by: Ondrej Fabry <ofabry@cisco.com>

2 files changed, 0 insertions, 4 deletions

diff --git a/src/vnet/lisp-cp/lisp.api b/src/vnet/lisp-cp/lisp.api
index 0e475856944..b1bea092273 100644
--- a/src/vnet/lisp-cp/lisp.api
+++ b/src/vnet/lisp-cp/lisp.api
@@ -626,13 +626,11 @@ define lisp_eid_table_vni_dump
 };
 
 /** \brief reply to lisp_eid_table_vni_dump
-    @param client_index - opaque cookie to identify the sender
     @param context - sender context, to match reply w/ request
     @param vni - virtual network instance
  */
 define lisp_eid_table_vni_details
 {
-  u32 client_index;
   u32 context;
   u32 vni;
 };
diff --git a/src/vnet/lisp-cp/one.api b/src/vnet/lisp-cp/one.api
index 32ac70220c5..7f0f5a9fbb1 100644
--- a/src/vnet/lisp-cp/one.api
+++ b/src/vnet/lisp-cp/one.api
@@ -835,13 +835,11 @@ define one_eid_table_vni_dump
 };
 
 /** \brief reply to one_eid_table_vni_dump
-    @param client_index - opaque cookie to identify the sender
     @param context - sender context, to match reply w/ request
     @param vni - virtual network instance
  */
 define one_eid_table_vni_details
 {
-  u32 client_index;
   u32 context;
   u32 vni;
 };