From: Slava Monich <slava.monich@jolla.com>
To: ofono@ofono.org
Subject: Re: [PATCH] mbpi: Parse gsm provider name
Date: Thu, 17 Apr 2014 21:29:59 +0300 [thread overview]
Message-ID: <53501DA7.5000301@jolla.com> (raw)
In-Reply-To: <534FF5EA.3000900@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Hi Denis,
> Hi Slava,
>
> Please do not top-post on this mailing list.
ah, sorry.
>
> On 04/17/2014 03:24 AM, Slava Monich wrote:
>> Hi Denis,
>> It's for custom provisioning plugins.
>>
>> Service provider name is passed to the provisioning plugin but not used
>> there at all. This patch makes it possible to utilize it for AP matching.
>>
> I still do not understand. SPN is passed to the provisioning plugin via
> get_settings. I do not see any need for it to be stored in
> ofono_gprs_provision_data struct. How is it going to be used by the core?
I agree that there is no need to for it to be returned by the
provisioning plugin to the core but it's the same structure used by
mbpi.c to return the result of parsing serviceproviders.xml to the
provisioning plugin. Side effect of sharing the structure between two
interfaces.
If instead I changed the interface between mbpi and provisioning plugin
and kept the interface with the core intact, would that look acceptable
to you?
Thanks,
-Slava
next prev parent reply other threads:[~2014-04-17 18:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:00 [PATCH] mbpi: Parse gsm provider name Slava Monich
2014-04-17 4:07 ` Denis Kenzior
2014-04-17 8:24 ` Slava Monich
2014-04-17 15:40 ` Denis Kenzior
2014-04-17 18:29 ` Slava Monich [this message]
2014-04-17 22:12 ` Denis Kenzior
2014-04-17 23:22 ` Slava Monich
2014-04-18 0:58 ` Denis Kenzior
2014-04-18 12:02 ` Slava Monich
2014-04-18 14:56 ` 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=53501DA7.5000301@jolla.com \
--to=slava.monich@jolla.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.