mgw_fsm: use LOG_MAP() to log error

Change-Id: Ic543a3c17eddf4b1da51172223eccaa62a441fd3
---
M src/osmo-hnbgw/mgw_fsm.c
1 file changed, 3 insertions(+), 3 deletions(-)


git pull ssh://gerrit.osmocom.org:29418/osmo-hnbgw refs/changes/60/40160/1

diff --git a/src/osmo-hnbgw/mgw_fsm.c b/src/osmo-hnbgw/mgw_fsm.c
index d44a6e3..26233d2 100644
--- a/src/osmo-hnbgw/mgw_fsm.c
+++ b/src/osmo-hnbgw/mgw_fsm.c
@@ -886,9 +886,9 @@
 		/* NOTE: This situation is a corner-case. We may end up here when the co-located MGW caused a problem
 		 * on the way between RANAP RAB Assignment Request and RANAP RAB Assignment Response. */
 
-		LOGP(DMGW, LOGL_ERROR,
-		     "%s() rua_ctx_id=%d, no MGW fsm -- sending Iu-Release-Request!\n",
-		     __func__, map->rua_ctx_id);
+		LOG_MAP(map, DMGW, LOGL_ERROR,
+			"%s() no MGW fsm -- sending Iu-Release-Request!\n",
+			__func__);
 
 		/* Send a release request, to make sure that the MSC is aware of the problem. */
 		tx_release_req(map);

