From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Support 51.011 EFecc format.
Date: Wed, 06 Jan 2010 14:28:29 -0600 [thread overview]
Message-ID: <201001061428.31547.denkenz@gmail.com> (raw)
In-Reply-To: <fb249edb0912181558l6cbc9079u2895d3422c11c5dd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
Hi Andrew,
> Here's a patch following 1. but I think you can take either patch.
> Note that we already know that no file gets cached until imsi is
> retrieved, imsi doesn't get retrieved before EFphase and EFphase
> isn't read before our PIN situation is sorted out.
Patch has been applied, thanks.
Regards,
-Denis
parent reply other threads:[~2010-01-06 20:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <fb249edb0912181558l6cbc9079u2895d3422c11c5dd@mail.gmail.com>]
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=201001061428.31547.denkenz@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