dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Dumitrescu,
	Cristian"
	<cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] MAINTAINERS: claim metering, sched and pkt framework
Date: Mon, 09 Feb 2015 18:08:14 +0100	[thread overview]
Message-ID: <2357398.2rVM9BA9Nq@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126323094EF-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>

2015-02-09 16:18, Dumitrescu, Cristian:
> > About cfgfile, we are still waiting for the cleanup in qos_sched example:
> > 	http://dpdk.org/ml/archives/dev/2014-October/006774.html
> > Do you have news?

> We are working on some enhancements on librte_cfg for release 2.1, so in
> order to avoid unnecessary code churn, it is probably better to have the
> librte_cfgfile changes done first, then have a subsequent patch on qos_sched.

Why not deduplicating now?

  parent reply	other threads:[~2015-02-09 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 13:13 [PATCH] MAINTAINERS: claim metering, sched and pkt framework Gonzalez Monroy, Sergio
     [not found] ` <91383E96CE459D47BCE92EFBF5CE73B004F46E1D-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-02-09 15:14   ` Thomas Monjalon
2015-02-09 16:18     ` Dumitrescu, Cristian
     [not found]       ` <3EB4FA525960D640B5BDFFD6A3D89126323094EF-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-02-09 17:08         ` Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-04 15:53 Cristian Dumitrescu
     [not found] ` <1423065205-13134-1-git-send-email-cristian.dumitrescu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-02-09  0:42   ` Zhang, Helin

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=2357398.2rVM9BA9Nq@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 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).