DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, bernard.iremonger@intel.com,
	jingjing.wu@intel.com, wenzhuo.lu@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] testpmd: fix memory leak for dscp table
Date: Sun, 18 Nov 2018 21:36:02 +0100	[thread overview]
Message-ID: <3483543.ap0HWNepZy@xps> (raw)
In-Reply-To: <20181114115859.160722-1-jasvinder.singh@intel.com>

14/11/2018 12:58, Jasvinder Singh:
> Fix memory leak for dscp table reported by coverity
> 
> Coverity ID: 326961
> Fixes: 281eeb8afc55 ("app/testpmd: add commands for metering and policing")
> CC: stable@dpdk.org
> 
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>

Applied, thanks

      reply	other threads:[~2018-11-18 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 11:58 [dpdk-dev] " Jasvinder Singh
2018-11-18 20:36 ` Thomas Monjalon [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=3483543.ap0HWNepZy@xps \
    --to=thomas@monjalon.net \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@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).