Open Source Telephony
 help / color / mirror / Atom feed
From: Ronald Tessier <ronald.tessier@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Add WSP_VALUE_TYPE_TEXT support in wsp_decode_application_id()
Date: Wed, 16 May 2012 17:45:24 +0200	[thread overview]
Message-ID: <4FB3CB94.1000108@linux.intel.com> (raw)
In-Reply-To: <1337177005-7385-1-git-send-email-jr_extern@vfnet.de>

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

Hi Jens,

On 05/16/2012 04:03 PM, Jens Rehsack wrote:
> From: Jens Rehsack<sno@NetBSD.org>
>
> ---
>   src/wsputil.c |    6 ++++++
>   1 Datei geändert, 6 Zeilen hinzugefügt(+)
>
> diff --git a/src/wsputil.c b/src/wsputil.c
> index 1b2b2b7..c4c9d62 100644
> --- a/src/wsputil.c
> +++ b/src/wsputil.c
> @@ -496,6 +496,12 @@ gboolean wsp_decode_application_id(struct wsp_header_iter *iter,
>   	 */
>   	if (wsp_header_iter_get_val_type(iter) == WSP_VALUE_TYPE_SHORT) {
>   		val = *pdu_val&  0x7f;
> +	} else if (wsp_header_iter_get_val_type(iter) == WSP_VALUE_TYPE_TEXT) {
> +		val_len = wsp_header_iter_get_val_len(iter);
> +		val = -1;
> +
> +		if (out_value)
> +			*out_value = pdu_val;
>   	} else {
>   		val_len = wsp_header_iter_get_val_len(iter);
>

Unless I miss something, if the application_id is given as TEXT (in the 
pdu) the *out_value will always be NULL (it will be set to the result of 
get_text_entry()).

I think you don't need to set val_len and val, you can just return TRUE 
after doing *out_value = pdu_val.

Best regards,

Ronald

  reply	other threads:[~2012-05-16 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 14:03 [PATCH] Add WSP_VALUE_TYPE_TEXT support in wsp_decode_application_id() Jens Rehsack
2012-05-16 15:45 ` Ronald Tessier [this message]
2012-05-16 16:18   ` Jens Rehsack
2012-05-18 12:59     ` Ronald Tessier
  -- strict thread matches above, loose matches on Subject: below --
2012-05-21 10:54 Jens Rehsack
2012-05-21 16:23 ` Ronald Tessier
2012-05-22  8:09   ` Jens Rehsack
2012-05-30  7:11     ` Jens Rehsack
2012-05-30  8:59 Jens Rehsack
2012-05-30 13:49 ` Denis Kenzior

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=4FB3CB94.1000108@linux.intel.com \
    --to=ronald.tessier@linux.intel.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