diff options
| author | Vadim Yanitskiy <vyanitskiy@sysmocom.de> | 2022-03-07 12:21:20 +0300 |
|---|---|---|
| committer | laforge <laforge@osmocom.org> | 2022-03-09 07:23:50 +0000 |
| commit | 8ec3f28fada3fe02d4fb3d86cdfe88c5cae497f8 (patch) | |
| tree | 3602c4037310c37a3aa1062e0881acef6acd8e27 /src/common/vty.c | |
| parent | d84567779c9dd17dffa6fa9905952af06b3cedc7 (diff) | |
VTY: fix ambiguity in BTS specific command definitions
Most of the BTS specific VTY commands restrict BTS number to '<0-0>',
while bts_c0_power_red_cmd has '<0-255>'. This confuses libosmovty:
OsmoBTS# bts ?
<0-0> BTS number
<0-255> BTS Number
OsmoBTS# bts 0 ?
% Ambiguous command.
OsmoBTS# bts 0 c0-power-red 0
% Ambiguous command.
Let's stick to '<0-0>', we don't support multiple BTS anyway.
Change-Id: I937ac421143678b97627c1bc4fe573831ce097f6
Diffstat (limited to 'src/common/vty.c')
| -rw-r--r-- | src/common/vty.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/common/vty.c b/src/common/vty.c index 97bd6589..89259997 100644 --- a/src/common/vty.c +++ b/src/common/vty.c @@ -1329,7 +1329,7 @@ DEFUN_HIDDEN(radio_link_timeout, radio_link_timeout_cmd, "bts <0-0> radio-link-t DEFUN(bts_c0_power_red, bts_c0_power_red_cmd, - "bts <0-255> c0-power-red <0-6>", + "bts <0-0> c0-power-red <0-6>", "BTS Specific Commands\n" BTS_NR_STR "BCCH carrier power reduction operation\n" "Power reduction value (in dB, even numbers only)\n") |