From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 4/9] Add parser for cause objects
Date: Mon, 29 Mar 2010 17:14:36 -0500 [thread overview]
Message-ID: <201003291714.36718.denkenz@gmail.com> (raw)
In-Reply-To: <1269879884-12741-4-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Hi Yang,
> ---
> src/stkutil.c | 35 +++++++++++++++++++++++++++++++++++
> 1 files changed, 35 insertions(+), 0 deletions(-)
>
> diff --git a/src/stkutil.c b/src/stkutil.c
> index ecd5639..8f4ff39 100644
> --- a/src/stkutil.c
> +++ b/src/stkutil.c
> @@ -687,6 +687,39 @@ static gboolean parse_dataobj_event_list(
> STK_DATA_OBJECT_TYPE_EVENT_LIST);
> }
>
> +/* Defined in TS 102.223 Section 8.26 */
> +static gboolean parse_dataobj_cause(
> + struct comprehension_tlv_iter *iter, void *user)
> +{
> + struct stk_common_byte_array *array = user;
> + const unsigned char *data;
> + unsigned int len;
> +
> + if (comprehension_tlv_iter_get_tag(iter) != STK_DATA_OBJECT_TYPE_CAUSE)
> + return FALSE;
> +
> + len = comprehension_tlv_iter_get_length(iter);
> + if ((len == 1) || (len > 30))
> + return FALSE;
So if we know the max length is 30 why do we bother g_mallocing here?
> +
> + if (len == 0) {
> + array->len = 0;
> + array->array = NULL;
> + return TRUE;
> + }
This won't work unfortunately. Cause is an optional element and cause with
length 0 has special meaning. We will have to include a boolean variable for
presence information somehow.
Regards,
-Denis
next prev parent reply other threads:[~2010-03-29 22:14 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 ` Denis Kenzior [this message]
2010-03-29 22:12 ` [PATCH 2/9] Add parser for items next action indicator objects Denis Kenzior
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 [PATCH 3/9] Add parser for event list objects Yang Gu
2010-03-29 16:04 ` [PATCH 4/9] Add parser for cause 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=201003291714.36718.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox