DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [pull-request] next-qos 18.11 pre-rc1
Date: Fri, 12 Oct 2018 11:06:53 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E7D8AAF@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1976670.pJK2cXVE7N@xps>



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, October 12, 2018 9:53 AM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [pull-request] next-qos 18.11 pre-rc1
> 
> Hi Cristian,
> 
> 08/10/2018 18:11, Cristian Dumitrescu:
> >   http://dpdk.org/git/next/dpdk-next-qos
> > ----------------------------------------------------------------
> > Jasvinder Singh (2):
> >       librte_sched: allocate memory on the given socket id
> >       app/testpmd: fix metering and policing cli command
> >
> > Krzysztof Kanas (1):
> >       app/testpmd: add commands for TM to mark pkts
> >
> > Rosen Xu (1):
> >       lib/librte_ethdev: expand queue threshold size of RED parameters
> >
> > Vivek Sharma (1):
> >       eal: use correct data type for bitmap slab operations
> 
> I see these warnings:
> 
> Headline too long:
>         lib/librte_ethdev: expand queue threshold size of RED parameters
> Is it candidate for Cc: stable@dpdk.org backport?
>         app/testpmd: fix metering and policing cli command
> 
> And about the titles, "librte_sched:" and "lib/librte_ethdev:" should be
> "sched:" and "ethdev:".
> 
> I fixed all when pulling.
> 

Thanks, Thomas.

      reply	other threads:[~2018-10-12 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 16:11 Cristian Dumitrescu
2018-10-12  8:53 ` Thomas Monjalon
2018-10-12 11:06   ` 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=3EB4FA525960D640B5BDFFD6A3D891268E7D8AAF@IRSMSX107.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --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).