From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>,
radoslaw.biernacki@linaro.org, stable@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] test: fix typo in memzone autotest
Date: Thu, 21 Dec 2017 18:19:42 +0000 [thread overview]
Message-ID: <5c1a7f3bfe6bbfc86f536541833de4ab1789a95c.1513866482.git.anatoly.burakov@intel.com> (raw)
Fixes: 71330483a193 ("test/memzone: fix memory leak")
Cc: radoslaw.biernacki@linaro.org
Cc: stable@dpdk.org
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
test/test/test_memzone.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/test/test/test_memzone.c b/test/test/test_memzone.c
index 1cf235a..aaffef9 100644
--- a/test/test/test_memzone.c
+++ b/test/test/test_memzone.c
@@ -948,11 +948,11 @@ test_memzone_basic(void)
return 0;
}
-static int memzone_calk_called;
+static int memzone_walk_called;
static void memzone_walk_clb(const struct rte_memzone *mz __rte_unused,
void *arg __rte_unused)
{
- memzone_calk_called = 1;
+ memzone_walk_called = 1;
}
static int
@@ -996,7 +996,7 @@ test_memzone(void)
printf("check memzone cleanup\n");
rte_memzone_walk(memzone_walk_clb, NULL);
- if (memzone_calk_called) {
+ if (memzone_walk_called) {
printf("there are some memzones left after test\n");
rte_memzone_dump(stdout);
return -1;
--
2.7.4
next reply other threads:[~2017-12-21 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 18:19 Anatoly Burakov [this message]
2017-12-21 18:19 ` [dpdk-dev] [PATCH 2/3] test: fix copypaste error " Anatoly Burakov
2017-12-21 18:19 ` [dpdk-dev] [PATCH 3/3] test: fix wrong test " Anatoly Burakov
2018-01-03 12:01 ` [dpdk-dev] [PATCH 1/3] test: fix typo " Radoslaw Biernacki
2018-01-17 23:35 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
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=5c1a7f3bfe6bbfc86f536541833de4ab1789a95c.1513866482.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=radoslaw.biernacki@linaro.org \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=stable@dpdk.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).