commit | 8cd74407ab4269736296d1cc9bbbf68940d343a7 | [log] [tgz] |
---|---|---|
author | Harald Welte <laforge@osmocom.org> | Fri Dec 04 22:24:47 2020 +0100 |
committer | Harald Welte <laforge@osmocom.org> | Sat Dec 05 12:06:42 2020 +0100 |
tree | 90949c1e87ed77f195c7b55237329d3b58359213 | |
parent | 6c4c6f08ae13d89b375584988ed1f0556417a7cf [diff] |
gb_proxy: Rename gbproxy_peer to gbproxy_bvc I cannot really read the code while it contains its historical weird naming. A "peer" used to be a strange amalgamation of NSE + BVC, while in reality we can have any number of BVC on top of each NSE. We recently started to split the peer into a gbproxy_nse_peer + gbproxy_peer. This takes it one step further and renames gbproxy_peer to gbproxy_bvc, as that's really what it is. Change-Id: Iae01067282a6401f6af4cab731202872d2cdb080