osmo-trx[master]: trx_vty.c: fix: use CONFIG_NODE as parent by default

Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/8083 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia0600a46d19825806e5aed9257b6c57c3907808b Gerrit-PatchSet: 1 Gerrit-Project: osmo-trx Gerrit-Branch: master

[MERGED] osmo-trx[master]: trx_vty.c: fix: use CONFIG_NODE as parent by default

Harald Welte has submitted this change and it was merged. Change subject: trx_vty.c: fix: use CONFIG_NODE as parent by default .. trx_vty.c: fix: use CONFIG_NODE as parent by default There are some configuration nodes, which

osmo-trx[master]: trx_vty.c: fix: use CONFIG_NODE as parent by default

Patch Set 1: Code-Review+1 as explained in OS#3250, the go_parent action here can be a lot simpler, but this change would fix it as well. Now we need a +2 from Tom. -- To view, visit https://gerrit.osmocom.org/8083 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType:

osmo-trx[master]: trx_vty.c: fix: use CONFIG_NODE as parent by default

Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/8083 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia0600a46d19825806e5aed9257b6c57c3907808b Gerrit-PatchSet: 1 Gerrit-Project: osmo-trx Gerrit-Branch: master

[PATCH] osmo-trx[master]: trx_vty.c: fix: use CONFIG_NODE as parent by default

Review at https://gerrit.osmocom.org/8083 trx_vty.c: fix: use CONFIG_NODE as parent by default There are some configuration nodes, which are handled by extenral libraries, such as libosmoctrl. So, when switching back to the parent node, this should be kept in mind. Instead of aborting, let's