From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kirill Rybalchenko <kirill.rybalchenko@intel.com>, dev@dpdk.org
Cc: andrey.chilikin@intel.com, jingjing.wu@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix potential memory leak
Date: Mon, 6 Nov 2017 23:06:33 -0800 [thread overview]
Message-ID: <9f57104d-b3f4-fb2a-1288-24894b4639ba@intel.com> (raw)
In-Reply-To: <1509617621-24850-1-git-send-email-kirill.rybalchenko@intel.com>
On 11/2/2017 3:13 AM, Kirill Rybalchenko wrote:
> Fix potential memory leak in cmd_ddp_info_parsed() function.
Coverity issue: 195044
> Fixes: a8e005696c7b ("app/testpmd: get ddp profile protocol info")
>
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2017-11-07 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 10:13 Kirill Rybalchenko
2017-11-07 7:06 ` Ferruh Yigit [this message]
2017-11-07 7:07 ` Ferruh Yigit
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=9f57104d-b3f4-fb2a-1288-24894b4639ba@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrey.chilikin@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=kirill.rybalchenko@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).