From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 1/2] common: add long dial string support
Date: Mon, 22 Nov 2010 05:00:24 -0600 [thread overview]
Message-ID: <4CEA4D48.3000301@gmail.com> (raw)
In-Reply-To: <4CE5104B.9080305@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Hi Andras,
On 11/18/2010 05:38 AM, Arun Ravindran wrote:
> Hi Denis, Marcel, Andras,
>
>> include/types.h | 2 +-
>> src/common.c | 12 ++++++------
>> 2 files changed, 7 insertions(+), 7 deletions(-)
>>
>> diff --git a/include/types.h b/include/types.h
>> index ba2481f..b3d2247 100644
>> --- a/include/types.h
>> +++ b/include/types.h
>> @@ -76,7 +76,7 @@ struct ofono_error {
>> int error;
>> };
>>
>> -#define OFONO_MAX_PHONE_NUMBER_LENGTH 20
>> +#define OFONO_MAX_PHONE_NUMBER_LENGTH 120
>>
>> struct ofono_phone_number {
>> char number[OFONO_MAX_PHONE_NUMBER_LENGTH + 1];
>> diff --git a/src/common.c b/src/common.c
>> index b5b9a6f..de5a508 100644
>> --- a/src/common.c
>> +++ b/src/common.c
>> @@ -253,7 +253,7 @@ gboolean valid_phone_number_format(const char
>> *number)
>> if (number[i]>= '0'&& number[i]<= '9')
>> continue;
>>
>> - if (number[i] == '*' || number[i] == '#')
>> + if (number[i] == '*' || number[i] == '#' || number[i] == 'p')
>> continue;
>>
> This function is used to check the phone number as valid in other places
> too.
>
> Is it right to allow sms sending to numbers with '*', '#' and 'p' in it?
> I think ofono should return an error for the sms case.
>
Arun has nailed it, hacking valid_phone_number_format is not the right
way to go. You need to separate this out a bit for the particular usecase.
Regards,
-Denis
next prev parent reply other threads:[~2010-11-22 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 17:39 [PATCH 0/2] Long dial string support Andras Domokos
2010-11-16 17:39 ` [RFC PATCH 1/2] common: add long " Andras Domokos
2010-11-18 11:38 ` Arun Ravindran
2010-11-22 11:00 ` Denis Kenzior [this message]
2010-11-16 17:39 ` [RFC PATCH 2/2] isimodem/voicecall: " Andras Domokos
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=4CEA4D48.3000301@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.