patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: declan.doherty@intel.com
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	stable@dpdk.org
Subject: [dpdk-stable] [PATCH 8/9] app/crypto-perf: fix error message
Date: Wed, 21 Jun 2017 07:41:53 +0100	[thread overview]
Message-ID: <20170621064154.25124-9-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <20170621064154.25124-1-pablo.de.lara.guarch@intel.com>

Fixes: f6cefe253cc8 ("app/crypto-perf: add range/list of sizes")
CC: stable@dpdk.org

Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
 app/test-crypto-perf/cperf_options_parsing.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/test-crypto-perf/cperf_options_parsing.c b/app/test-crypto-perf/cperf_options_parsing.c
index d172671..63ba37c 100644
--- a/app/test-crypto-perf/cperf_options_parsing.c
+++ b/app/test-crypto-perf/cperf_options_parsing.c
@@ -312,7 +312,7 @@ parse_buffer_sz(struct cperf_options *opts, const char *arg)
 					&opts->min_buffer_size,
 					&opts->max_buffer_size);
 		if (ret < 0) {
-			RTE_LOG(ERR, USER1, "failed to parse burst size/s\n");
+			RTE_LOG(ERR, USER1, "failed to parse buffer size/s\n");
 			return -1;
 		}
 		opts->buffer_size_count = ret;
-- 
2.9.4

  parent reply	other threads:[~2017-06-21 14:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170621064154.25124-1-pablo.de.lara.guarch@intel.com>
2017-06-21  6:41 ` [dpdk-stable] [PATCH 1/9] crypto/aesni_mb: remove assert check Pablo de Lara
2017-06-21  6:41 ` [dpdk-stable] [PATCH 2/9] test/crypto: fix wrong AAD setting Pablo de Lara
2017-06-21 17:39   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-22 10:40     ` De Lara Guarch, Pablo
2017-06-21  6:41 ` [dpdk-stable] [PATCH 6/9] examples/l2fwd-crypto: fix application help Pablo de Lara
2017-06-21 16:43   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-21  6:41 ` [dpdk-stable] [PATCH 7/9] examples/l2fwd-crypto: fix auth info display Pablo de Lara
2017-06-21 16:44   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
2017-06-21  6:41 ` Pablo de Lara [this message]
2017-06-21 16:39   ` [dpdk-stable] [dpdk-dev] [PATCH 8/9] app/crypto-perf: fix error message Trahe, Fiona
2017-06-21  6:41 ` [dpdk-stable] [PATCH 9/9] doc: fix typo in l2fwd-crypto usage Pablo de Lara
2017-06-21 17:44   ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona
     [not found] ` <20170622120235.46063-1-pablo.de.lara.guarch@intel.com>
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 1/9] crypto/aesni_mb: remove assert check Pablo de Lara
2017-06-23 12:50     ` Declan Doherty
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 2/9] test/crypto: fix wrong AAD setting Pablo de Lara
2017-06-23  9:56     ` Trahe, Fiona
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 6/9] examples/l2fwd-crypto: fix application help Pablo de Lara
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 7/9] examples/l2fwd-crypto: fix auth info display Pablo de Lara
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 8/9] app/crypto-perf: fix error message Pablo de Lara
2017-06-22 12:02   ` [dpdk-stable] [PATCH v2 9/9] doc: fix typo in l2fwd-crypto usage Pablo de Lara

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=20170621064154.25124-9-pablo.de.lara.guarch@intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --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).