From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Nikita Kozlov <nikita@elyzion.net>
Cc: dev@dpdk.org, "Dai, Wei" <wei.dai@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] app/test: fix a segfault when lpm_perf_autotest is run more than 1 time
Date: Sun, 06 Nov 2016 23:55:14 +0100 [thread overview]
Message-ID: <2191381.BBdCHmE80k@xps13> (raw)
In-Reply-To: <49759EB36A64CF4892C1AFEC9231E8D63A2EB3E8@PGSMSX106.gar.corp.intel.com>
> > num_route_entries need to be reseted.
> >
> > Fixes: 17d60f5b5eea ("app/test: remove large IPv4 LPM data file")
> >
> > Signed-off-by: Nikita Kozlov <nikita@elyzion.net>
> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
> Tested-by: Wei Dai <wei.dai@intel.com>
> Acked-by: Wei Dai <wei.dai@intel.com>
Appplied, thanks
next prev parent reply other threads:[~2016-11-06 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 10:47 [dpdk-dev] [PATCH] " Nikita Kozlov
2016-11-01 11:20 ` [dpdk-dev] [PATCH v2] " Nikita Kozlov
2016-11-01 11:55 ` [dpdk-dev] [PATCH v3] " Nikita Kozlov
2016-11-03 3:28 ` Dai, Wei
2016-11-06 22:55 ` Thomas Monjalon [this message]
2016-11-01 11:20 ` [dpdk-dev] [PATCH] " Bruce Richardson
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=2191381.BBdCHmE80k@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nikita@elyzion.net \
--cc=wei.dai@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).