From: Bruce Richardson <bruce.richardson@intel.com>
To: Nikita Kozlov <nikita@elyzion.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app/test: fix a segfault when lpm_perf_autotest is run more than 1 time
Date: Tue, 1 Nov 2016 11:20:59 +0000 [thread overview]
Message-ID: <20161101112059.GA112052@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20161101104742.12307-1-nikita@elyzion.net>
On Tue, Nov 01, 2016 at 11:47:42AM +0100, Nikita Kozlov wrote:
> num_route_entries need to be reseted.
> ---
> app/test/test_lpm_perf.c | 1 +
> 1 file changed, 1 insertion(+)
>
You forgot your signoff on the patch, but I confirm it does indeed fix
the issue. Also, as fixes line is needed to identify the commit that
introduced the bug.
Tested-by: Bruce Richardson <bruce.richardson@intel.com>
prev parent reply other threads:[~2016-11-01 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 10:47 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
2016-11-01 11:20 ` Bruce Richardson [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=20161101112059.GA112052@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nikita@elyzion.net \
/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).