From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sim: Fix the quirk handling of CPIN for Wavecom Q2XXX
Date: Wed, 31 Oct 2012 16:16:16 -0500 [thread overview]
Message-ID: <50919520.8090600@gmail.com> (raw)
In-Reply-To: <1351726211-10255-1-git-send-email-holger@freyther.de>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
Hi Holger,
On 10/31/2012 06:30 PM, Holger Hans Peter Freyther wrote:
> From: Holger Hans Peter Freyther<hfreyther@sysmocom.de>
>
> Commit 1ccecfe01eb7f9f4d1d931814deb66ef37840b73 added the quirk
> handling for the Q2XXX module but it missed the first part of
> the Wavecom quirk handling.
>
> If decode_at_error is not fed with OK the error variable will be
> set to an error and the sim_pin_query_cb will exit before doing
> any notifications. This started to happen after git commit
> 72ce19bf3e87b5e73c053f7ea1095a5006f1aea9).
> ---
> drivers/atmodem/sim.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/atmodem/sim.c b/drivers/atmodem/sim.c
> index cf3345c..89445bb 100644
> --- a/drivers/atmodem/sim.c
> +++ b/drivers/atmodem/sim.c
> @@ -980,7 +980,8 @@ static void at_cpin_cb(gboolean ok, GAtResult *result, gpointer user_data)
> int len = sizeof(at_sim_name) / sizeof(*at_sim_name);
> const char *final = g_at_result_final_response(result);
>
> - if (sd->vendor == OFONO_VENDOR_WAVECOM&& ok&& strlen(final)> 7)
> + if ((sd->vendor == OFONO_VENDOR_WAVECOM ||
> + sd->vendor == OFONO_VENDOR_WAVECOM_Q2XXX)&& ok&& strlen(final)> 7)
Patch looks good to me, but can you please make sure this line doesn't
go above 80 characters per our coding guidelines? See doc/coding-style.txt
> decode_at_error(&error, "OK");
> else
> decode_at_error(&error, final);
Regards,
-Denis
prev parent reply other threads:[~2012-10-31 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 23:30 [PATCH] sim: Fix the quirk handling of CPIN for Wavecom Q2XXX Holger Hans Peter Freyther
2012-10-31 21:16 ` 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=50919520.8090600@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.