From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] librte_cfgfile rework and extension
Date: Mon, 1 Jun 2015 08:34:30 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891263236FCEB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1432913219-11589-1-git-send-email-maciejx.t.gajdzica@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Maciej Gajdzica
> Sent: Friday, May 29, 2015 4:27 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/3] librte_cfgfile rework and extension
>
> From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
>
> This patchset provide extension to librte_cfgfile to overcome limit of 64
> characters for entry value and add line continue feature.
>
> Pawel Wodkowski (3):
> librte_cfgfile: fix code formating in header file
> librte_compat: fix macro deffinition
> librte_cfgfile: rework
>
> lib/librte_cfgfile/Makefile | 2 +-
> lib/librte_cfgfile/rte_cfgfile.c | 792 ++++++++++++++++++++++-------
> lib/librte_cfgfile/rte_cfgfile.h | 52 +-
> lib/librte_cfgfile/rte_cfgfile_version.map | 8 +
> lib/librte_compat/rte_compat.h | 2 +-
> 5 files changed, 649 insertions(+), 207 deletions(-)
>
> --
> 1.9.1
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
prev parent reply other threads:[~2015-06-01 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 15:26 Maciej Gajdzica
2015-05-29 15:26 ` [dpdk-dev] [PATCH 1/3] librte_cfgfile: fix code formating in header file Maciej Gajdzica
2015-05-29 15:26 ` [dpdk-dev] [PATCH 2/3] librte_compat: fix macro deffinition Maciej Gajdzica
2015-06-15 9:12 ` Thomas Monjalon
2015-05-29 15:26 ` [dpdk-dev] [PATCH 3/3] librte_cfgfile: rework Maciej Gajdzica
2015-06-15 9:29 ` Thomas Monjalon
2015-06-01 8:34 ` Dumitrescu, Cristian [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=3EB4FA525960D640B5BDFFD6A3D891263236FCEB@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=maciejx.t.gajdzica@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).