From: Thomas Monjalon <thomas@monjalon.net>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
bernard.iremonger@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] lib/librte_flow_classify: fix memory leak issue
Date: Thu, 25 Jan 2018 23:30:56 +0100 [thread overview]
Message-ID: <10197565.HTIDjyuCRh@xps> (raw)
In-Reply-To: <b38ccb55-6a70-955d-89e9-c8f8071eb2a9@intel.com>
22/01/2018 15:49, Ferruh Yigit:
> On 1/22/2018 2:14 PM, Jasvinder Singh wrote:
> > Free allocated memory of the rule if not added to the table.
> >
> > Coverity issue: 257032
> > Fixes: 50bdac5916d9 ("flow_classify: remove table id parameter from API")
> >
> > Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
Note: lib/librte_ is not needed in the title beginning.
prev parent reply other threads:[~2018-01-25 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:14 Jasvinder Singh
2018-01-22 14:49 ` Ferruh Yigit
2018-01-25 22:30 ` 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=10197565.HTIDjyuCRh@xps \
--to=thomas@monjalon.net \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=john.mcnamara@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).