From: Thomas Monjalon <thomas@monjalon.net>
To: Kuba Kozak <kubax.kozak@intel.com>, jacekx.piasecki@intel.com
Cc: dev@dpdk.org, bruce.richardson@intel.com,
deepak.k.jain@intel.com, michalx.k.jastrzebski@intel.com
Subject: Re: [PATCH v6 0/5] Rework cfgfile API to enable apps config file support
Date: Mon, 09 Oct 2017 00:55:16 +0200 [thread overview]
Message-ID: <2155345.JQTbFBeCJG@xps> (raw)
In-Reply-To: <1506073490-45399-1-git-send-email-kubax.kozak@intel.com>
22/09/2017 11:44, Kuba Kozak:
> New API for cfgfile library allows to create a cfgfile at runtime, add new
> section, add entry in a section, update existing entry and save cfgfile
> structure to INI file - opens up the possibility to have applications
> dynamically build up a proper DPDK configuration, rather than
> having to have a pre-existing one. Due the new API functions, simplification
> of load() function was made. One new unit test to TEST app was added. It
> contains an example of a large INI file whose parsing requires multiple
> reallocation of memory.
I have fixed the map file (switched to 17.11) and
applied, thanks.
prev parent reply other threads:[~2017-10-08 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 9:44 [PATCH v6 0/5] Rework cfgfile API to enable apps config file support Kuba Kozak
2017-09-22 9:44 ` [PATCH v6 1/5] cfgfile: remove EAL dependency Kuba Kozak
2017-09-22 9:44 ` [PATCH v6 2/5] cfgfile: change existing API functions Kuba Kozak
2017-09-22 9:44 ` [PATCH v6 3/5] cfgfile: add APIs for cfgfile modification Kuba Kozak
2017-09-22 9:44 ` [PATCH v6 4/5] cfgfile: rework of load function Kuba Kozak
2017-09-22 9:44 ` [PATCH v6 5/5] test/cfgfile: add new unit test Kuba Kozak
2017-10-08 22:55 ` Thomas Monjalon [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=2155345.JQTbFBeCJG@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=jacekx.piasecki@intel.com \
--cc=kubax.kozak@intel.com \
--cc=michalx.k.jastrzebski@intel.com \
/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.