From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 0/3] Add null text/alpha identifier and icon check handling
Date: Wed, 05 Jan 2011 10:07:53 -0600 [thread overview]
Message-ID: <4D249759.6040602@gmail.com> (raw)
In-Reply-To: <1294180923-12241-1-git-send-email-jeevaka.badrappan@elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Hi Jeevaka,
On 01/04/2011 04:42 PM, Jeevaka Badrappan wrote:
> Hi,
>
> Following patch adds the missing "text/alpha identifier and icon"
> check handling.
>
> As per the ETSI 102 223 section 6.8, Text string is only required in
> response to a GetInkey or GetInput proactive command. So, there is no
> need to add any specific handling for null or empty strings cases.
>
> As per the ETSI TS 102 223 section 6.5.4, "If the terminal receives an
> icon, and either an empty or no alpha identifier/text string is given
> by the UICC, than the terminal shall reject the command with general"
> result "Command data not understood by terminal"."
>
> Regards,
> Jeevaka
>
All three have been applied, thanks.
Regards,
-Denis
next prev parent reply other threads:[~2011-01-05 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 22:42 [PATCH 0/3] Add null text/alpha identifier and icon check handling Jeevaka Badrappan
2011-01-04 22:42 ` [PATCH 1/3] stkutil: Allocate for empty string in text dataobj Jeevaka Badrappan
2011-01-04 22:42 ` [PATCHv2 2/3] stkutil: add missing text and icon check Jeevaka Badrappan
2011-01-04 22:42 ` [PATCH 3/3] unit: add error status support for failure cases Jeevaka Badrappan
2011-01-05 16:07 ` Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-31 12:30 [PATCH 0/3] Add null text/alpha identifier and icon check handling Jeevaka Badrappan
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=4D249759.6040602@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.