From: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
To: ofono@ofono.org
Subject: Re: [PATCHv4 3/3] Mobile broadband provider info plugin
Date: Tue, 30 Aug 2011 15:57:54 +0300 [thread overview]
Message-ID: <4E5CDE52.8030507@intel.com> (raw)
In-Reply-To: <4E544E27.3030204@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Hello Denis,
On 08/24/2011 04:04 AM, Denis Kenzior wrote:
> However, I'm still wondering whether setting data->match_found is
> enough. Here's the example I'm thinking of:
>
> <provider>
> <name>Major Operator</name>
> <network-id mcc="555" mnc="55"/>
> <apn>...</apn>
> </provider>
>
> <provider>
> <name>MVNO running on Major Operator</name>
> <network-id mcc="555" mnc="55"/>
> <apn>...</apn>
> </provider>
>
> If the Major Operator provides MAX_APN apns, then wouldn't this cause us
> to return the APNs from Major Operator, even though this is a conflict
> and we might potentially want APNs from MVNO?
>
> If this is indeed such a conflicted case then we need to let the user
> decide, not return any results as they're potentially erroneous.
Thanks for the comments. Please take a look at the PATCHv5 on the list, which
addresses this and other issues too.
Regards,
Oleg
--
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
prev parent reply other threads:[~2011-08-30 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 11:23 [PATCHv4 0/3] Mobile broadband provider info plugin Oleg Zhurakivskyy
2011-08-25 11:23 ` [PATCHv4 1/3] Mobile broadband provider info plugin makefile changes Oleg Zhurakivskyy
2011-08-25 11:23 ` [PATCHv4 2/3] Mobile broadband provider info plugin autoconf support Oleg Zhurakivskyy
2011-08-25 11:23 ` [PATCHv4 3/3] Mobile broadband provider info plugin Oleg Zhurakivskyy
2011-08-24 1:04 ` Denis Kenzior
2011-08-30 12:57 ` Oleg Zhurakivskyy [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=4E5CDE52.8030507@intel.com \
--to=oleg.zhurakivskyy@intel.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