From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Check if ussd is busy when doing ss
Date: Thu, 09 Sep 2010 09:07:29 -0500 [thread overview]
Message-ID: <4C88EA21.3020302@gmail.com> (raw)
In-Reply-To: <1283739595-11903-1-git-send-email-yang.gu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hi Yang,
On 09/05/2010 09:19 PM, Yang Gu wrote:
> It's still not clear how ss and ussd interfere with each other. Current
> decision is each ss (call-barring, call-forwarding, etc.) has
> interference with ussd, but there is no interference within these ss.
> That is, call-barring has interference with ussd, but call-barring has
> no interference with call-forwarding.
Patch has been applied, but I broke it up into four patches.
Are you planning to take care of cb_ss_control, cb_ss_password,
cf_ss_control and cs_ss_control busy conditions separately?
Regards,
-Denis
next prev parent reply other threads:[~2010-09-09 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 2:19 [PATCH] Check if ussd is busy when doing ss Yang Gu
2010-09-09 14:07 ` Denis Kenzior [this message]
2010-09-10 8:27 ` Gu, Yang
2010-09-13 13:18 ` Pekka Pessi
2010-09-14 9:51 ` Gu, Yang
2010-09-14 12:46 ` Pekka Pessi
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=4C88EA21.3020302@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