Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] avoid stk atom is removed when sim pin is blocked
Date: Wed, 11 Sep 2013 12:41:57 -0500	[thread overview]
Message-ID: <5230AB65.2030704@gmail.com> (raw)
In-Reply-To: <1378921861-6238-1-git-send-email-caiwen.zhang@intel.com>

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

Hi Caiwen,

On 09/11/2013 12:51 PM, caiwen.zhang(a)intel.com wrote:
> From: Caiwen Zhang <caiwen.zhang@intel.com>
>
> When sim pin is blocked after input wrong pin code three times,
> modem will change to pre-sim status, at this time, STK function
> should be available. stk atoms shouldn't be removed.

Can you please provide a reference to a 3GPP / ETSI document which 
states that this is the case?
> ---
>   src/modem.c |    7 ++++++-
>   src/stk.c   |    4 ++++
>   2 files changed, 10 insertions(+), 1 deletion(-)
>

Regards,
-Denis


  reply	other threads:[~2013-09-11 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 17:51 [PATCH] avoid stk atom is removed when sim pin is blocked caiwen.zhang
2013-09-11 17:41 ` Denis Kenzior [this message]
2013-09-12  1:14   ` Zhang, Caiwen
2013-09-12 13:32     ` Denis Kenzior
2013-09-16 12:33       ` Zhang, Caiwen

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=5230AB65.2030704@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