Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sim: Fix the quirk handling of CPIN for Wavecom
Date: Thu, 01 Nov 2012 05:00:20 -0500	[thread overview]
Message-ID: <50924834.4050504@gmail.com> (raw)
In-Reply-To: <1351760703-28090-1-git-send-email-holger@freyther.de>

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

Hi Holger,

On 11/01/2012 04:05 AM, Holger Hans Peter Freyther wrote:
> From: Holger Hans Peter Freyther<hfreyther@sysmocom.de>
>
> The Wavecom Q2XXX support broke in commit 72ce19bf3e87b5e73c053f7ea1.
> This is because at_cpin_cb called decode_at_error with final and not
> with OK. This lead to an error being set in the error variable and the
> new code returns early when an error is set.
>
> The addition of the terminator in at_sim_probe for Wavecom broke in
> git commit ac524be99f8c72a2593e4ffcecad8beea7679e55 because
> terminators can not be added on cloned chats.
>
> Move the addition of the terminator from the atmodem to the wavecom
> plugin. Use the same terminator for Q2XXX and the normal Wavecom
> class. The WAVECOM terminator has been tested on a Q2XXX modem.
>
> Apply the CPIN quirk for both WAVECOM and WAVECOM_Q2XXX inside the
> sim.c file. Introduce needs_wavecom_sim_quirk to handle it for
> WAVECOM and WAVECOM_Q2XXX.
> ---
>   drivers/atmodem/sim.c |   24 +++++++++---------------
>   plugins/wavecom.c     |    2 ++
>   2 files changed, 11 insertions(+), 15 deletions(-)
>

Patch has been applied, however I broke it up into two with accordance 
to our patch submission guidelines.  Please see HACKING 'Submitting 
patches' section.

Regards,
-Denis


      parent reply	other threads:[~2012-11-01 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01  9:05 [PATCH] sim: Fix the quirk handling of CPIN for Wavecom Holger Hans Peter Freyther
2012-11-01  9:22 ` Holger Freyther
2012-11-01 10:00 ` Denis Kenzior [this message]

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=50924834.4050504@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