From cb6ad70994dc7686f1c89d803fcca1081b5ef32b Mon Sep 17 00:00:00 2001 From: Holger Hans Peter Freyther Date: Tue, 22 Jul 2014 15:00:52 +0200 Subject: mgcp: Change API to remove memory management from the name Jacob pointed out that "free_endp" refers to the memory of the endpoint being freed. What we want is actually a way to release an endpoint (and the resource it allocated) or in the case of the testcase/testapp initialize the data structure correctly. Introduce two names for that. --- openbsc/src/osmo-bsc_mgcp/mgcp_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'openbsc/src/osmo-bsc_mgcp') diff --git a/openbsc/src/osmo-bsc_mgcp/mgcp_main.c b/openbsc/src/osmo-bsc_mgcp/mgcp_main.c index 8c3808a28..16fb72231 100644 --- a/openbsc/src/osmo-bsc_mgcp/mgcp_main.c +++ b/openbsc/src/osmo-bsc_mgcp/mgcp_main.c @@ -181,7 +181,7 @@ static int read_call_agent(struct osmo_fd *fd, unsigned int what) /* is checking in_addr.s_addr == INADDR_LOOPBACK making it more secure? */ for (i = 1; i < reset_trunk->number_endpoints; ++i) - mgcp_free_endp(&reset_trunk->endpoints[i]); + mgcp_release_endp(&reset_trunk->endpoints[i]); } return 0; -- cgit v1.2.3