From 90a07524d195b93d5050d7fdbd6675846fe3c7ff Mon Sep 17 00:00:00 2001
From: Neels Hofmeyr <neels@hofmeyr.de>
Date: Wed, 29 Jul 2020 01:22:11 +0200
Subject: [PATCH] bsc CBSP: cosmetic: rename f_cbsp_init_tail() to
 f_expect_cbsp_restart()

It might be part of initialization, but what this function does is expect to
receive a CBSP RESTART, period.

Change-Id: Ieffe70cf43eb79b798d93717bbce294ee809f0e2
---
 bsc/BSC_Tests_CBSP.ttcn | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/bsc/BSC_Tests_CBSP.ttcn b/bsc/BSC_Tests_CBSP.ttcn
index 413ab5df8..8b7954da7 100644
--- a/bsc/BSC_Tests_CBSP.ttcn
+++ b/bsc/BSC_Tests_CBSP.ttcn
@@ -125,9 +125,9 @@ private function f_cbsp_init_server(float guard_timeout := 30.0) runs on cbsp_te
 		mtc.stop;
 		}
 	}
-	f_cbsp_init_tail();
+	f_expect_cbsp_restart();
 }
-private function f_cbsp_init_tail() runs on cbsp_test_CT {
+private function f_expect_cbsp_restart() runs on cbsp_test_CT {
 	interleave {
 	[] CBSP[0].receive(tr_CBSP_Recv(?, tr_CBSP_RESTART(?, CBSP_BC_MSGT_CBS, CBSP_RI_DATA_LOST)));
 	/* should we also expect a restart for emergency related messages? */