ligang/vpp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vrrp: do not define _details as autoreply

Browse Source 
Without this, _details_reply messages also end up defined;
which is not intended, as there are no _details_t_handler functions.

Type: fix
Fixes: 39e9428b90

Change-Id: Id052b00b00623ca92e5ddce4cc5e1bdfbb1031db
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
This commit is contained in:
Vratko Polak
2020-02-18 19:12:47 +01:00
committed by Dave Barach
parent ffd15463b2
commit 3fccd0278c
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/plugins/vrrp/vrrp.api
View File

@@ -5,7 +5,7 @@
*
*/
option version = "1.0.0";
option version = "1.0.1";
import "vnet/interface_types.api";
import "vnet/ip/ip_types.api";
@@ -167,7 +167,7 @@ define vrrp_vr_peer_dump {
@param n_peer_addrs - number of peer addresses
@param peer_addrs - peer addresses
*/
autoreply define vrrp_vr_peer_details {
define vrrp_vr_peer_details {
u32 client_index;
u32 context;
vl_api_interface_index_t sw_if_index;
@@ -233,7 +233,7 @@ define vrrp_vr_track_if_dump {
@param n_ifs - number of tracked interfaces
@param ifs - array of tracked interface data
*/
autoreply define vrrp_vr_track_if_details {
define vrrp_vr_track_if_details {
u32 client_index;
u32 context;
vl_api_interface_index_t sw_if_index;
@@ -242,4 +242,3 @@ autoreply define vrrp_vr_track_if_details {
u8 n_ifs;
vl_api_vrrp_vr_track_if_t ifs[n_ifs];
};