All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Cristian Dumitrescu
	<cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [v2 20/23] librte_cfgfile: interpret config files
Date: Thu, 16 Oct 2014 18:46:10 +0200	[thread overview]
Message-ID: <10629744.mhUtJ8hJ7T@xps13> (raw)
In-Reply-To: <1401905319-8882-21-git-send-email-cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Hi Cristian,

2014-06-04 19:08, Cristian Dumitrescu:
> This library provides a tool to interpret config files that have standard
> structure.
> 
> It is used by the Packet Framework examples/ip_pipeline sample application.
> 
> It originates from examples/qos_sched sample application and now it makes
> this code available as a library for other sample applications to use.
> The code duplication with qos_sched sample app to be addressed later.

4 months ago, you said that this duplication will be adressed later.
Neither you nor anyone at Intel submitted a patch to clean up that.
I just want to be sure that "later" doesn't mean "never" because
I'm accepting another "later" word for cleaning old filtering API.

Maybe you just forgot it so please prove me that I'm right to accept
"later" clean-up, in general.

Thanks
-- 
Thomas

  parent reply	other threads:[~2014-10-16 16:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 18:08 [v2 00/23] Packet Framework Cristian Dumitrescu
     [not found] ` <1401905319-8882-1-git-send-email-cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-06-04 18:08   ` [v2 01/23] librte_lpm: rule_is_present Cristian Dumitrescu
2014-06-04 18:08   ` [v2 02/23] mbuf: meta-data Cristian Dumitrescu
2014-06-04 18:08   ` [v2 03/23] Packet Framework librte_port: Port API Cristian Dumitrescu
2014-06-04 18:08   ` [v2 04/23] Packet Framework librte_port: ethdev ports Cristian Dumitrescu
2014-06-04 18:08   ` [v2 05/23] Packet Framework librte_port: ring ports Cristian Dumitrescu
2014-06-04 18:08   ` [v2 06/23] Packet Framework librte_port: IPv4 frag port Cristian Dumitrescu
2014-06-04 18:08   ` [v2 07/23] Packet Framework librte_port: IPv4 reassembly Cristian Dumitrescu
2014-06-04 18:08   ` [v2 08/23] Packet Framework librte_port: hierarchical scheduler port Cristian Dumitrescu
2014-06-04 18:08   ` [v2 09/23] Packet Framework librte_port: Source/Sink ports Cristian Dumitrescu
2014-06-04 18:08   ` [v2 10/23] Packet Framework librte_port: Build infrastructure Cristian Dumitrescu
2014-06-04 18:08   ` [v2 11/23] Packet Framework librte_table: Table API Cristian Dumitrescu
2014-06-04 18:08   ` [v2 12/23] Packet Framework librte_table: LPM IPv4 table Cristian Dumitrescu
2014-06-04 18:08   ` [v2 13/23] Packet Framework librte_table: LPM IPv6 table Cristian Dumitrescu
2014-06-04 18:08   ` [v2 14/23] Packet Framework librte_table: ACL table Cristian Dumitrescu
2014-06-04 18:08   ` [v2 15/23] Packet Framework librte_table: Hash tables Cristian Dumitrescu
2014-06-04 18:08   ` [v2 16/23] Packet Framework librte_table: array table Cristian Dumitrescu
2014-06-04 18:08   ` [v2 17/23] Packet Framework librte_table: Stub table Cristian Dumitrescu
2014-06-04 18:08   ` [v2 18/23] Packet Framework librte_table: Build infrastructure Cristian Dumitrescu
2014-06-04 18:08   ` [v2 19/23] Packet Framework librte_pipeline: Pipeline Cristian Dumitrescu
2014-06-04 18:08   ` [v2 20/23] librte_cfgfile: interpret config files Cristian Dumitrescu
     [not found]     ` <1401905319-8882-21-git-send-email-cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-10-16 16:46       ` Thomas Monjalon [this message]
2014-10-17 18:16         ` Dumitrescu, Cristian
     [not found]           ` <3EB4FA525960D640B5BDFFD6A3D891262E090572-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-10-17 18:50             ` Thomas Monjalon
2014-06-04 18:08   ` [v2 21/23] Packet Framework performance application Cristian Dumitrescu
2014-06-04 18:08   ` [v2 22/23] Packet Framework IPv4 pipeline sample app Cristian Dumitrescu
     [not found]     ` <1401905319-8882-23-git-send-email-cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-06-09  9:11       ` Olivier MATZ
     [not found]         ` <53957A4E.6090401-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-06-09 10:49           ` Dumitrescu, Cristian
     [not found]             ` <3EB4FA525960D640B5BDFFD6A3D891261B1C2354-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-09 12:13               ` Olivier MATZ
     [not found]                 ` <5395A4F6.7050609-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-06-09 13:25                   ` Dumitrescu, Cristian
     [not found]                     ` <3EB4FA525960D640B5BDFFD6A3D891261B1C2415-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-09 15:51                       ` Olivier MATZ
2014-06-04 18:08   ` [v2 23/23] Packet Framework unit tests Cristian Dumitrescu
2014-06-05 11:01   ` [v2 00/23] Packet Framework De Lara Guarch, Pablo
2014-06-05 11:43   ` Cao, Waterman
2014-06-05 14:40   ` Ivan Boule
     [not found]     ` <53908147.6030804-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-06-17  1:27       ` 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=10629744.mhUtJ8hJ7T@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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.