diff options
| author | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2014-02-09 20:03:38 +0100 |
|---|---|---|
| committer | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2014-02-09 20:05:17 +0100 |
| commit | 10f0bdecad8d711ccc5fcc04bb0be0adf11a7902 (patch) | |
| tree | 0b729fa8fe004a38f99f3737ab0242a09e492abd /src/gsm | |
| parent | f4f5a8489c427432b12b09ebba456c3ca25106a3 (diff) | |
lapd: Use the right struct for the talloc_zero_array call
I saw this while playing with talloc pools and wondered why
lapd_core is creating a log_info. Use the right struct for
the array.
Diffstat (limited to 'src/gsm')
| -rw-r--r-- | src/gsm/lapd_core.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/gsm/lapd_core.c b/src/gsm/lapd_core.c index ccfa4b43..0d8f1282 100644 --- a/src/gsm/lapd_core.c +++ b/src/gsm/lapd_core.c @@ -291,8 +291,8 @@ void lapd_dl_init(struct lapd_datalink *dl, uint8_t k, uint8_t v_range, if (!tall_lapd_ctx) tall_lapd_ctx = talloc_named_const(NULL, 1, "lapd context"); - dl->tx_hist = (struct lapd_history *) talloc_zero_array(tall_lapd_ctx, - struct log_info, dl->range_hist); + dl->tx_hist = talloc_zero_array(tall_lapd_ctx, + struct lapd_history, dl->range_hist); } /* reset to IDLE state */ |