From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Guduri Prathyusha <gprathyusha@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] librte_cfgfile: add section num entries by index
Date: Tue, 1 Aug 2017 12:36:25 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA8770E@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <3240514.oRFImOiSkL@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Monday, July 31, 2017 10:10 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; Guduri Prathyusha
> <gprathyusha@caviumnetworks.com>
> Subject: Re: [dpdk-dev] [PATCH] librte_cfgfile: add section num entries by
> index
>
> 27/04/2017 08:51, Guduri Prathyusha:
> > rte_cfgfile_section_num_entries_by_index() is added to get the number
> of
> > entries of a section when multiple sections of the same name are
> > present.
> >
> > Signed-off-by: Guduri Prathyusha <gprathyusha@caviumnetworks.com>
> > ---
> > lib/librte_cfgfile/rte_cfgfile.c | 13 +++++++++++++
> > lib/librte_cfgfile/rte_cfgfile.h | 20 ++++++++++++++++++++
> > 2 files changed, 33 insertions(+)
>
> Cristian, this is an old patch not reviewed.
> Any comment please?
Do you need this reviewed for this release, or can it wait until the next release?
I have a few patches on my list to review (librte_cfgfile, librte_sched), I will make this review a priority for next release cycle.
next prev parent reply other threads:[~2017-08-01 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 6:51 Guduri Prathyusha
2017-07-31 21:10 ` Thomas Monjalon
2017-08-01 12:36 ` Dumitrescu, Cristian [this message]
2017-08-01 12:42 ` Thomas Monjalon
2017-09-04 6:12 ` Prathyusha, Guduri
2017-09-04 10:58 ` Bruce Richardson
2017-09-04 11:28 ` Guduri Prathyusha
2017-09-15 13:59 ` Thomas Monjalon
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=3EB4FA525960D640B5BDFFD6A3D891267BA8770E@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=gprathyusha@caviumnetworks.com \
--cc=thomas@monjalon.net \
/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).