From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/9] Add parser for items next action indicator objects
Date: Mon, 29 Mar 2010 17:12:43 -0500 [thread overview]
Message-ID: <201003291712.44314.denkenz@gmail.com> (raw)
In-Reply-To: <1269879884-12741-2-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3200 bytes --]
Hi Yang,
> ---
> src/stkutil.c | 38 ++++++++++++++++++++++++++++++++++++++
> src/stkutil.h | 5 +++++
> 2 files changed, 43 insertions(+), 0 deletions(-)
>
> diff --git a/src/stkutil.c b/src/stkutil.c
> index 9a02658..b997752 100644
> --- a/src/stkutil.c
> +++ b/src/stkutil.c
> @@ -67,6 +67,34 @@ static gboolean parse_dataobj_common_bool(struct
> comprehension_tlv_iter *iter, return TRUE;
> }
>
> +/* For data object that only has a byte array with variable length */
> +static gboolean parse_dataobj_common_byte_array(
> + struct comprehension_tlv_iter *iter, void *user,
Can we have this function take two arguments, namely the array and the len? I
don't like introducing stk_common_byte_array as an exported data type.
> + enum stk_data_object_type type)
> +{
> + struct stk_common_byte_array *array = user;
> + const unsigned char *data;
> + unsigned int len;
> +
> + if (comprehension_tlv_iter_get_tag(iter) != type)
> + return FALSE;
> +
> + len = comprehension_tlv_iter_get_length(iter);
> + if (len < 1)
> + return FALSE;
> +
> + data = comprehension_tlv_iter_get_data(iter);
> + array->len = len;
> +
> + array->array = g_try_malloc(len);
> + if (array->array == NULL)
> + return FALSE;
> +
> + memcpy(array->array, data, len);
> +
> + return TRUE;
> +}
> +
> /* Defined in TS 102.223 Section 8.1 */
> static gboolean parse_dataobj_address(struct comprehension_tlv_iter *iter,
> void *user)
> @@ -643,6 +671,14 @@ static gboolean
> parse_dataobj_network_measurement_results( return TRUE;
> }
>
> +/* Defined in TS 102.223 Section 8.24 */
> +static gboolean parse_dataobj_items_next_action_indicator(
> + struct comprehension_tlv_iter *iter, void *user)
> +{
> + return parse_dataobj_common_byte_array(iter, user,
> + STK_DATA_OBJECT_TYPE_ITEMS_NEXT_ACTION_INDICATOR);
> +}
> +
So in theory this object does not need to be malloced. We know that it is max
of 127 bytes long according to the rules of comprehension tlvs. Might as well
treat it that way. I seriously want to avoid g_malloc / g_free unless
absolutely necessary.
> /* Defined in TS 102.223 Section 8.31 */
> static gboolean parse_dataobj_icon_id(struct comprehension_tlv_iter *iter,
> void *user)
> @@ -760,6 +796,8 @@ static dataobj_handler handler_for_type(enum
> stk_data_object_type type) return parse_dataobj_help_request;
> case STK_DATA_OBJECT_TYPE_NETWORK_MEASUREMENT_RESULTS:
> return parse_dataobj_network_measurement_results;
> + case STK_DATA_OBJECT_TYPE_ITEMS_NEXT_ACTION_INDICATOR:
> + return parse_dataobj_items_next_action_indicator;
> case STK_DATA_OBJECT_TYPE_ICON_ID:
> return parse_dataobj_icon_id;
> case STK_DATA_OBJECT_TYPE_IMMEDIATE_RESPONSE:
> diff --git a/src/stkutil.h b/src/stkutil.h
> index a9495de..cd43ae2 100644
> --- a/src/stkutil.h
> +++ b/src/stkutil.h
> @@ -266,6 +266,11 @@ enum stk_tone_type {
> STK_TONE_TYPE_MELODY_8 = 0x47
> };
>
> +struct stk_common_byte_array {
> + unsigned int len;
> + unsigned char *array;
> +};
> +
> /* Defined in TS 102.223 Section 8.1 */
> struct stk_address {
> unsigned char ton_npi;
>
next prev parent reply other threads:[~2010-03-29 22:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:24 [PATCH 1/9] Add parser for network measurement results objects Yang Gu
2010-03-29 16:24 ` [PATCH 2/9] Add parser for items next action indicator objects Yang Gu
2010-03-29 16:24 ` [PATCH 3/9] Add parser for event list objects Yang Gu
2010-03-29 16:24 ` [PATCH 4/9] Add parser for cause objects Yang Gu
2010-03-29 16:24 ` [PATCH 5/9] Add parser for location status objects Yang Gu
2010-03-29 16:24 ` [PATCH 6/9] Add parser for transaction identifier objects Yang Gu
2010-03-29 16:24 ` [PATCH 7/9] Add parser for call control requested action objects Yang Gu
2010-03-29 16:24 ` [PATCH 8/9] Add the macro for icon qualifier Yang Gu
2010-03-29 16:24 ` [PATCH 9/9] Add parser for item icon identifier list objects Yang Gu
2010-03-29 22:21 ` Denis Kenzior
2010-03-29 22:20 ` [PATCH 8/9] Add the macro for icon qualifier Denis Kenzior
2010-03-29 22:19 ` [PATCH 6/9] Add parser for transaction identifier objects Denis Kenzior
2010-03-29 22:14 ` [PATCH 4/9] Add parser for cause objects Denis Kenzior
2010-03-29 22:12 ` Denis Kenzior [this message]
2010-03-29 22:21 ` [PATCH 1/9] Add parser for network measurement results objects Denis Kenzior
-- strict thread matches above, loose matches on Subject: below --
2010-03-29 16:03 Yang Gu
2010-03-29 16:03 ` [PATCH 2/9] Add parser for items next action indicator objects Yang Gu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003291712.44314.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.