tree 0b846f9081aeca52c991e34eecf52491ae85976a
parent 29993a913895ce966f3935b89bfc35455b3d37bd
author Alexander Chemeris <Alexander.Chemeris@gmail.com> 1591435225 +0300
committer laforge <laforge@osmocom.org> 1597257498 +0000

timeslot_fsm: Name TS FSM instances on allocation.

Before this patch FSM instances of configured but not connected BTS's
look like this:
FSM Instance Name: 'timeslot[0x612000004a20]', ID: '(null)'
 Log-Level: 'DEBUG', State: 'NOT_INITIALIZED'

Now they look like this:
FSM Instance Name: 'timeslot(0-0-7-NONE)[0x612000004a20]', ID: '0-0-7-NONE'
 Log-Level: 'DEBUG', State: 'NOT_INITIALIZED'

which makes it possible to attribute them to where they belong.
Otherwise, they look like lingering or leaking unattributed FSM
instances.

Change-Id: Idc74ea142b96323b48826f8a52e13e45d535512a