From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 0/2] Add provisioning plugin from configuration file
Date: Tue, 21 Feb 2017 11:12:32 -0600 [thread overview]
Message-ID: <d31d59d2-c420-e880-5877-e0e33ed0a8f8@gmail.com> (raw)
In-Reply-To: <20170217144448.23940-1-c.ronco@kerlink.fr>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Hi Christophe,
On 02/17/2017 08:44 AM, Christophe Ronco wrote:
> The goal of this plugin is to provision APN and other internet context details
> from a configuration file.
>
> The modification from what I sent yesterday:
> - do not use storage functions anymore
> - changed section names to be able to add other type of sections in the future
>
> Christophe Ronco (2):
> provision: add plugin to provision from config file
> plugins: support for provisioning from config file
>
> Makefile.am | 4 ++
> plugins/file-provision.c | 170 +++++++++++++++++++++++++++++++++++++++++++++++
Strictly speaking there was no need to separate these into two patches.
If you're adding a new plugin, then build system changes belong together
with the code additions. Just for future reference.
> 2 files changed, 174 insertions(+)
> create mode 100644 plugins/file-provision.c
>
I squished together patch 1 & 2 into a single commit and applied. Thanks!
Regards,
-Denis
prev parent reply other threads:[~2017-02-21 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d9dfde3c-2b28-197f-f257-a7451d9871ed@kerlink.fr>
2017-02-08 12:24 ` provisioning APN using mbpi plugin Christophe Ronco
2017-02-08 16:54 ` Denis Kenzior
2017-02-16 16:46 ` Christophe Ronco
2017-02-16 18:02 ` Denis Kenzior
2017-02-17 14:44 ` [PATCH 0/2] Add provisioning plugin from configuration file Christophe Ronco
2017-02-17 14:44 ` [PATCH 1/2] provision: add plugin to provision from config file Christophe Ronco
2017-02-17 14:44 ` [PATCH 2/2] plugins: support for provisioning " Christophe Ronco
2017-02-21 17:12 ` 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=d31d59d2-c420-e880-5877-e0e33ed0a8f8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox