DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH 2/4] test: fix compilation when RTE_APP_TEST_DEBUG was set
Date: Wed, 15 Jun 2016 14:01:47 +0100	[thread overview]
Message-ID: <1465995709-32278-3-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <1465995709-32278-1-git-send-email-pablo.de.lara.guarch@intel.com>

Compilation error:

app/test/test_cryptodev.c: In function ‘create_gcm_operation’:
app/test/test_cryptodev.c:3619:18: error: ‘struct rte_crypto_op’ has no member named ‘digest’
     ut_params->op->digest.data,
                  ^
app/test/test_cryptodev.c:3620:18: error: ‘struct rte_crypto_op’ has no member named ‘digest’
     ut_params->op->digest.length);
                  ^
app/test/test_cryptodev.c:3662:41: error: ‘struct rte_crypto_op’ has no member named ‘iv’
  rte_hexdump(stdout, "iv:", ut_params->op->iv.data, iv_pad_len);
                                         ^
app/test/test_cryptodev.c:3664:17: error: ‘struct rte_crypto_op’ has no member named ‘additional_auth’
    ut_params->op->additional_auth.data, aad_len);

Fixes: eec136f3c54fc ("aesni_gcm: add driver for AES-GCM crypto operations")

Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
 app/test/test_cryptodev.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index c5b5fb3..5674534 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -2404,8 +2404,8 @@ create_gcm_operation(enum rte_crypto_cipher_operation op,
 		rte_memcpy(sym_op->auth.digest.data, auth_tag, auth_tag_len);
 #ifdef RTE_APP_TEST_DEBUG
 		rte_hexdump(stdout, "digest:",
-				ut_params->op->digest.data,
-				ut_params->op->digest.length);
+				sym_op->auth.digest.data,
+				sym_op->auth.digest.length);
 #endif
 	}
 
@@ -2447,9 +2447,9 @@ create_gcm_operation(enum rte_crypto_cipher_operation op,
 	rte_memcpy(sym_op->auth.aad.data, aad, aad_len);
 
 #ifdef RTE_APP_TEST_DEBUG
-	rte_hexdump(stdout, "iv:", ut_params->op->iv.data, iv_pad_len);
+	rte_hexdump(stdout, "iv:", sym_op->cipher.iv.data, iv_pad_len);
 	rte_hexdump(stdout, "aad:",
-			ut_params->op->additional_auth.data, aad_len);
+			sym_op->auth.aad.data, aad_len);
 #endif
 	sym_op->cipher.data.length = data_len;
 	sym_op->cipher.data.offset = aad_buffer_len + iv_pad_len;
-- 
2.5.0

  parent reply	other threads:[~2016-06-15 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 13:01 [dpdk-dev] [PATCH 0/4] Refactor of debug information on cryptodev tests Pablo de Lara
2016-06-15 13:01 ` [dpdk-dev] [PATCH 1/4] test: remove useless hexdump include Pablo de Lara
2016-06-15 13:01 ` Pablo de Lara [this message]
2016-06-15 13:01 ` [dpdk-dev] [PATCH 3/4] test: remove unnecessary hexdump_mbuf_data and HEXDUMP Pablo de Lara
2016-06-15 13:01 ` [dpdk-dev] [PATCH 4/4] app: add new TEST_HEXDUMP macro Pablo de Lara
2016-06-15 14:03 ` [dpdk-dev] [PATCH 0/4] Refactor of debug information on cryptodev tests De Lara Guarch, Pablo
2016-06-15 14:11 ` [dpdk-dev] [PATCH v2 " Pablo de Lara
2016-06-15 14:11   ` [dpdk-dev] [PATCH v2 1/4] test: remove useless hexdump include Pablo de Lara
2016-06-15 14:11   ` [dpdk-dev] [PATCH v2 2/4] test: fix compilation when RTE_APP_TEST_DEBUG was set Pablo de Lara
2016-06-15 14:11   ` [dpdk-dev] [PATCH v2 3/4] test: remove unnecessary hexdump_mbuf_data and HEXDUMP Pablo de Lara
2016-06-15 14:11   ` [dpdk-dev] [PATCH v2 4/4] app: add new TEST_HEXDUMP macro Pablo de Lara
2016-06-15 14:42   ` [dpdk-dev] [PATCH v2 0/4] Refactor of debug information on cryptodev tests Zhang, Roy Fan
2016-06-20 15:48     ` 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=1465995709-32278-3-git-send-email-pablo.de.lara.guarch@intel.com \
    --to=pablo.de.lara.guarch@intel.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).