Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 2/2] sim: Read EFust and EFest
Date: Mon, 23 Aug 2010 14:31:17 -0500	[thread overview]
Message-ID: <4C72CC85.6090208@gmail.com> (raw)
In-Reply-To: <1282197935-9118-2-git-send-email-yang.gu@intel.com>

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

Hi Yang,

On 08/19/2010 01:05 AM, Yang Gu wrote:
> ---
>  src/sim.c     |   75 +++++++++++++++++++++++++++++++++++++++-
>  src/simutil.c |   18 ++++++++++
>  src/simutil.h |  105 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 196 insertions(+), 2 deletions(-)

This patch has now been applied.  However, please send a follow on patch
to support EFsst from 11.11 and 51.011.  The file id is the same as
EFust, however the structure is actually different.

Regards,
-Denis

  reply	other threads:[~2010-08-23 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19  6:05 [PATCH 1/2] Make function reset_available() return void Yang Gu
2010-08-19  6:05 ` [PATCH 2/2] sim: Read EFust and EFest Yang Gu
2010-08-23 19:31   ` Denis Kenzior [this message]
2010-08-19  8:15 ` [PATCH 1/2] Make function reset_available() return void Marcel Holtmann

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=4C72CC85.6090208@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