All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Fix: simplify isimodem call-barring driver.
Date: Tue, 23 Mar 2010 16:53:13 -0500	[thread overview]
Message-ID: <201003231653.14125.denkenz@gmail.com> (raw)
In-Reply-To: <1269366372-19526-1-git-send-email-ppessi@gmail.com>

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

Hi Pekka,

> From: Pekka Pessi <Pekka.Pessi@nokia.com>
> 
> Add support for lock codes AG and AC (MMI codes 333 and 353. respectively).

First of all, please keep your commit messages less than 72 characters long 
and headings less than 50 characters long.

Secondly, please keep your patches whitespace clean, there are several cases 
of spaces being used instead of tabs for indentation.

> ---
>  drivers/isimodem/call-barring.c |  153
>  ++++++++++++--------------------------- drivers/isimodem/ss.h           | 
>   28 ++++----
>  2 files changed, 63 insertions(+), 118 deletions(-)
> 
> diff --git a/drivers/isimodem/call-barring.c
>  b/drivers/isimodem/call-barring.c index 6487ae8..b0246fa 100644
> --- a/drivers/isimodem/call-barring.c
> +++ b/drivers/isimodem/call-barring.c
> @@ -48,6 +48,28 @@ struct barr_data {
>  	GIsiClient *client;
>  };

> 
> +	DBG("lock code %s (%u) old password %s new password %s\n",
> +	    lock, ss_code, old_passwd, new_passwd);

Here is an instance of whitespace error.

> -	if (g_isi_request_make(bd->client, msg, sizeof(msg), SS_TIMEOUT,
> +	if (cbd &&
> +	    g_isi_request_make(bd->client, msg, sizeof(msg), SS_TIMEOUT,
>  				set_passwd_resp_cb, cbd))
>  		return;

Here's another one..

>  enum ss_codes {
> -	SS_GSM_ALL_FORWARDINGS = 0x02,
> -	SS_GSM_ALL_COND_FORWARDINGS = 0x04,
> -	SS_GSM_FORW_UNCONDITIONAL = 0x15,
> -	SS_GSM_BARR_ALL_OUT = 0x21,
> -	SS_GSM_BARR_ALL_IN = 0x23,
> -	SS_GSM_CALL_WAITING = 0x2B,
> -	SS_GSM_FORW_NO_REPLY = 0x3D,
> -	SS_GSM_FORW_NO_REACH = 0x3E,
> -	SS_GSM_FORW_BUSY = 0x43,
> -	SS_GSM_ALL_BARRINGS = 0x014A,
> -	SS_GSM_BARR_OUT_INTER = 0x014B,
> -	SS_GSM_BARR_OUT_INTER_EXC_HOME = 0x014C,
> -	SS_GSM_BARR_ALL_IN_ROAM = 0x015F
> +	SS_GSM_ALL_FORWARDINGS = 002,
> +	SS_GSM_ALL_COND_FORWARDINGS = 004,

Are you sure this isn't octal syntax?  It still works, but you might simply 
use 2 and 4  here.

> +	SS_GSM_FORW_UNCONDITIONAL = 21,
> +	SS_GSM_BARR_ALL_OUT = 33,
> +	SS_GSM_OUTGOING_BARR_SERV = 333,
> +	SS_GSM_INCOMING_BARR_SERV = 353,
> +	SS_GSM_BARR_ALL_IN = 35,
> +	SS_GSM_CALL_WAITING = 43,
> +	SS_GSM_FORW_NO_REPLY = 61,
> +	SS_GSM_FORW_NO_REACH = 62,
> +	SS_GSM_FORW_BUSY = 67,
> +	SS_GSM_ALL_BARRINGS = 330,
> +	SS_GSM_BARR_OUT_INTER = 331,
> +	SS_GSM_BARR_OUT_INTER_EXC_HOME = 332,
> +	SS_GSM_BARR_ALL_IN_ROAM = 351,
>  };

From now on we'll require all enum values to be tab aligned so they're a bit 
easier to read.  See src/stkutil.h for reference.

Regards,
-Denis

  reply	other threads:[~2010-03-23 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 17:46 [PATCH] Fix: simplify isimodem call-barring driver ppessi
2010-03-23 21:53 ` Denis Kenzior [this message]
2010-03-24  8:05   ` Aki Niemi
2010-03-29 18:20   ` Pekka Pessi
  -- strict thread matches above, loose matches on Subject: below --
2010-03-29 18:15 ppessi
2010-03-29 18:17 ppessi
2010-03-29 20:40 ` 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=201003231653.14125.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 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.