From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 6/9] Add parser for transaction identifier objects
Date: Mon, 29 Mar 2010 17:19:05 -0500 [thread overview]
Message-ID: <201003291719.05509.denkenz@gmail.com> (raw)
In-Reply-To: <1269879884-12741-6-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Hi Yang,
> ---
> src/stkutil.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/src/stkutil.c b/src/stkutil.c
> index 3aae6bf..d573430 100644
> --- a/src/stkutil.c
> +++ b/src/stkutil.c
> @@ -748,6 +748,14 @@ static gboolean parse_dataobj_location_status(
> STK_DATA_OBJECT_TYPE_LOCATION_STATUS);
> }
>
> +/* Defined in TS 102.223 Section 8.28 */
> +static gboolean parse_dataobj_transaction_id(
> + struct comprehension_tlv_iter *iter, void *user)
> +{
> + return parse_dataobj_common_byte_array(iter, user,
> + STK_DATA_OBJECT_TYPE_TRANSACTION_ID);
> +}
> +
Again, the maximum size is 127, so lets avoid a g_malloc here.
> /* Defined in TS 102.223 Section 8.31 */
> static gboolean parse_dataobj_icon_id(struct comprehension_tlv_iter *iter,
> void *user)
> @@ -873,6 +881,8 @@ static dataobj_handler handler_for_type(enum
> stk_data_object_type type) return parse_dataobj_cause;
> case STK_DATA_OBJECT_TYPE_LOCATION_STATUS:
> return parse_dataobj_location_status;
> + case STK_DATA_OBJECT_TYPE_TRANSACTION_ID:
> + return parse_dataobj_transaction_id;
> case STK_DATA_OBJECT_TYPE_ICON_ID:
> return parse_dataobj_icon_id;
> case STK_DATA_OBJECT_TYPE_IMMEDIATE_RESPONSE:
>
Regards,
-Denis
next prev parent reply other threads:[~2010-03-29 22:19 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 ` Denis Kenzior [this message]
2010-03-29 22:14 ` [PATCH 4/9] Add parser for cause objects Denis Kenzior
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:04 [PATCH 5/9] Add parser for location status objects Yang Gu
2010-03-29 16:05 ` [PATCH 6/9] Add parser for transaction identifier 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=201003291719.05509.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.