From: David Christensen <drc@linux.vnet.ibm.com>
To: dev@dpdk.org
Cc: David Christensen <drc@linux.vnet.ibm.com>
Subject: [dpdk-dev] [PATCH v2 1/4] test: fix typo in print statement
Date: Mon, 6 May 2019 14:23:22 -0500 [thread overview]
Message-ID: <1557170602-99431-1-git-send-email-drc@linux.vnet.ibm.com> (raw)
Change "much" to "match" in a printf.
Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
---
v2:
* None
app/test/test_barrier.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/test_barrier.c b/app/test/test_barrier.c
index 82b572c..c219d56 100644
--- a/app/test/test_barrier.c
+++ b/app/test/test_barrier.c
@@ -252,7 +252,7 @@ struct lcore_plock_test {
/* race condition occurred, lock doesn't work properly */
if (sum[i] != pt[i].val || 2 * iter != pt[i].iter) {
- printf("error: local and shared sums don't much\n");
+ printf("error: local and shared sums don't match\n");
rc = -1;
}
}
--
1.8.3.1
next reply other threads:[~2019-05-06 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 19:23 David Christensen [this message]
2019-05-06 19:23 ` David Christensen
2019-05-07 10:41 ` Ananyev, Konstantin
2019-05-07 10:41 ` Ananyev, Konstantin
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=1557170602-99431-1-git-send-email-drc@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=dev@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).