From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 0/9] Emergency Mode
Date: Thu, 31 Mar 2011 19:43:08 +0200 [thread overview]
Message-ID: <1301593388.2572.147.camel@aeonflux> (raw)
In-Reply-To: <1301588312-6932-1-git-send-email-jeevaka.badrappan@elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
Hi Jeevaka,
> Following patch is a proposal for emergency mode. Test has been done
> with the phonesim.
>
> Listed down few important cases to give an overview of the state
> changes that happen in each case.
and I think we should turn this into a doc/emergency-call-handling.txt
and extend a bit. Especially with what is expected from the user/UI to
be done and what oFono will do for the user/UI.
Regards
Marcel
next prev parent reply other threads:[~2011-03-31 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 16:18 [RFC PATCH 0/9] Emergency Mode Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 1/9] dbus: Add __ofono_error_emergency_active Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 2/9] include: add ofono_modem_get_emergency_mode api Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 3/9] modem: " Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 4/9] modem: add Emergency property Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 5/9] modem: add increment/decrement emergency mode api Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 6/9] modem: modem state decoupled from rf state Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 7/9] modem: restrict operations allowed in emergency Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 8/9] voicecall: generalise emergency call check Jeevaka Badrappan
2011-03-31 16:18 ` [RFC PATCH 9/9] voicecall: add emergency mode handling Jeevaka Badrappan
2011-03-31 17:43 ` Marcel Holtmann [this message]
2011-03-31 22:47 ` [RFC PATCH 0/9] Emergency Mode Jeevaka.Badrappan
2011-04-05 5:00 ` 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=1301593388.2572.147.camel@aeonflux \
--to=marcel@holtmann.org \
--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