From 2768246e7a368b7b74f16fe9db8c8a5ce02c6c88 Mon Sep 17 00:00:00 2001 From: Vadim Yanitskiy Date: Wed, 17 Nov 2021 02:10:55 +0300 Subject: [PATCH] tdef: fix wrong path in documentation: tests/vty -> tests/tdef Change-Id: I2ba9a7a0ba9ad440c879d6a1da110d2fda49eb23 --- src/tdef.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/tdef.c b/src/tdef.c index 75b884a69..7741a4493 100644 --- a/src/tdef.c +++ b/src/tdef.c @@ -52,18 +52,18 @@ * By keeping separate osmo_tdef arrays, several groups of timers can be kept * separately. The VTY tests in tests/tdef/ showcase different schemes: * - * - \ref tests/vty/tdef_vty_config_root_test.c: + * - \ref tests/tdef/tdef_vty_config_root_test.c: * Keep several timer definitions in separately named groups: showcase the * osmo_tdef_vty_groups*() API. Each timer group exists exactly once. * - * - \ref tests/vty/tdef_vty_config_subnode_test.c: + * - \ref tests/tdef/tdef_vty_config_subnode_test.c: * Keep a single list of timers without separate grouping. * Put this list on a specific subnode below the CONFIG_NODE. * There could be several separate subnodes with timers like this, i.e. * continuing from this example, sets of timers could be separated by placing * timers in specific config subnodes instead of using the global group name. * - * - \ref tests/vty/tdef_vty_dynamic_test.c: + * - \ref tests/tdef/tdef_vty_dynamic_test.c: * Dynamically allocate timer definitions per each new created object. * Thus there can be an arbitrary number of independent timer definitions, one * per allocated object.