From: Thomas Monjalon <thomas@monjalon.net>
To: Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com>
Cc: dev@dpdk.org, Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
kkanas@caviumnetworks.com, cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix buffer leak in tm cmdline
Date: Thu, 26 Jul 2018 19:26:24 +0200 [thread overview]
Message-ID: <218947398.CCYfYaYgaB@xps> (raw)
In-Reply-To: <1530769547-8586-1-git-send-email-nithin.dabilpuram@caviumnetworks.com>
05/07/2018 07:45, Nithin Dabilpuram:
> Free the buffer allocated for shared_shaper_id array in
> case of configuration without shared shapers.
>
> Signed-off-by: Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com>
> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-07-26 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 5:45 Nithin Dabilpuram
2018-07-26 17:26 ` 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=218947398.CCYfYaYgaB@xps \
--to=thomas@monjalon.net \
--cc=bernard.iremonger@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=kkanas@caviumnetworks.com \
--cc=nithin.dabilpuram@caviumnetworks.com \
--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).