aboutsummaryrefslogtreecommitdiffstats
path: root/include/osmocom/core
diff options
context:
space:
mode:
authorMax <msuraev@sysmocom.de>2019-01-21 14:19:59 +0100
committerHarald Welte <laforge@gnumonks.org>2019-01-21 13:47:08 +0000
commitb27e6feb699712345373e87a48187dc622e4fa92 (patch)
tree0da011baa9a80a2f992430b38d9acfed71cdf782 /include/osmocom/core
parenta0c1cba28a661d9d5c7fcb092afe37e4bd70eeca (diff)
Rename msgb_wrap_with_TL()
This resolves an issue introduced in 84fb5bb6a09a6a358f98c654c84c3b99a0f24eef when msgb_wrap_with_TL() was introduced as an inline function with *exactly the same name* as in osmo-msc.git and openbsc.git. We *NEVER* do something like this. Functions moved from applications to library *MUST* always be renamed. This has been the case for almost a decade now. With this subsequent change we make sure the libosmocore function has a different name and doesn't clash. After this commit, old openbsc.git and osmo-bsc.git should again build fine. Change-Id: If1e851ac605c8d2fde3da565b0bd674ea6350c2e
Diffstat (limited to 'include/osmocom/core')
-rw-r--r--include/osmocom/core/msgb.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/osmocom/core/msgb.h b/include/osmocom/core/msgb.h
index b7c8422..f006b34 100644
--- a/include/osmocom/core/msgb.h
+++ b/include/osmocom/core/msgb.h
@@ -368,7 +368,7 @@ static inline void msgb_push_u32(struct msgb *msg, uint32_t word)
osmo_store32be(word, space);
}
-static inline unsigned char *msgb_wrap_with_TL(struct msgb *msgb, uint8_t tag)
+static inline unsigned char *msgb_push_tl(struct msgb *msgb, uint8_t tag)
{
uint8_t *data = msgb_push(msgb, 2);