From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "ndabilpuram@marvell.com" <ndabilpuram@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] testpmd: fix memory leak in iterator
Date: Thu, 21 Nov 2019 13:58:09 +0000 [thread overview]
Message-ID: <767a50e0-d105-93ce-3976-23149b57cf94@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260E2820B@IRSMSX108.ger.corp.intel.com>
On 11/21/2019 11:43 AM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Stephen Hemminger
>> Sent: Wednesday, November 20, 2019 11:26 PM
>> To: dev@dpdk.org
>> Cc: Stephen Hemminger <stephen@networkplumber.org>;
>> ndabilpuram@marvell.com; stable@dpdk.org
>> Subject: [dpdk-dev] [PATCH] testpmd: fix memory leak in iterator
>>
>> The RTE_FOREACH_MATCHING_DEV iterator requires that if a break is done
>> before the end of the loop, the function rte_eth_iterator_cleanup() must be
>> called.
>>
>> Fixes: 55e51c962432 ("app/testpmd: add device related commands")
>> Cc: ndabilpuram@marvell.com
>> Cc: stable@dpdk.org
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
>
> ./devtools/check-git-log.sh -1
> Wrong headline label:
> testpmd: fix memory leak in iterator
>
> Headline label should be app/testpmd
>
> Otherwise
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com
>
Applied to dpdk-next-net/master, thanks.
(fixed headline label while merging)
prev parent reply other threads:[~2019-11-21 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 23:26 [dpdk-stable] " Stephen Hemminger
2019-11-21 11:43 ` [dpdk-stable] [dpdk-dev] " Iremonger, Bernard
2019-11-21 13:58 ` 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=767a50e0-d105-93ce-3976-23149b57cf94@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ndabilpuram@marvell.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
/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).