DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: wangyunjian <wangyunjian@huawei.com>, dev@dpdk.org
Cc: jerry.lilijun@huawei.com, xudingke@huawei.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] test-pmd: fix memory leaks when mtr policer actions update fails
Date: Wed, 27 May 2020 23:57:52 +0100	[thread overview]
Message-ID: <1b8caf33-0ded-43fb-d37a-5a20a507b1dd@intel.com> (raw)
In-Reply-To: <1590371183-22636-1-git-send-email-wangyunjian@huawei.com>

On 5/25/2020 2:46 AM, wangyunjian wrote:
> From: Yunjian Wang <wangyunjian@huawei.com>
> 
> This patch fixes the Huawei internal coverity reported
> resource leak issue.
> 
> Fixes: e63b50162aa3 ("app/testpmd: clean metering and policing commands")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Updating commit log as following:

"
    app/testpmd: fix memory leaks on error path

    This patch fixes the resource leak issue.

    Fixes: e63b50162aa3 ("app/testpmd: clean metering and policing commands")
    Cc: stable@dpdk.org
"

1) Updated patch title
2) Removed reference to internal coverity, since others can't access it, this
information doesn't add value


Applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2020-05-27 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  1:46 [dpdk-dev] " wangyunjian
2020-05-25  6:51 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2020-05-26  2:04   ` wangyunjian
2020-05-26  7:13     ` Thomas Monjalon
2020-05-27  2:10       ` wangyunjian
2020-05-27  8:05         ` Thomas Monjalon
2020-05-27 22:57 ` Ferruh Yigit [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=1b8caf33-0ded-43fb-d37a-5a20a507b1dd@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerry.lilijun@huawei.com \
    --cc=stable@dpdk.org \
    --cc=wangyunjian@huawei.com \
    --cc=xudingke@huawei.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).