From 35b6b25433b4bc1c1f20cc9d0fa477591cb0e0e7 Mon Sep 17 00:00:00 2001 From: Philipp Maier Date: Tue, 15 Jun 2021 12:39:51 +0200 Subject: handover_cfg: add missing VTY_CMD_PREFIX in comment The comment that explains HO_CFG_ONE_MEMBER lacks VTY_CMD_PREFIX in the sample macro definistion. Change-Id: I80db198178cfd1e8669589eb3b468766f0c30ea2 --- include/osmocom/bsc/handover_cfg.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/osmocom/bsc/handover_cfg.h b/include/osmocom/bsc/handover_cfg.h index 342d5e458..6e003af94 100644 --- a/include/osmocom/bsc/handover_cfg.h +++ b/include/osmocom/bsc/handover_cfg.h @@ -53,7 +53,7 @@ static inline const char *tdma2a(bool val) /* The HO_CFG_ONE_MEMBER macro gets redefined, depending on whether to define struct members, * function declarations or definitions... It is of the format * HO_CFG_ONE_MEMBER(TYPE, NAME, DEFAULT_VAL, - * VTY_CMD, VTY_CMD_ARG, VTY_ARG_EVAL, + * VTY_CMD_PREFIX, VTY_CMD, VTY_CMD_ARG, VTY_ARG_EVAL, * VTY_WRITE_FMT, VTY_WRITE_CONV, * VTY_DOC) * Then using HO_CFG_ALL_MEMBERS can save a lot of code dup in defining API declaration, API -- cgit v1.2.3