From: Radu Nicolau <radu.nicolau@intel.com>
To: Jingjing Wu <jingjing.wu@intel.com>, Beilei Xing <beilei.xing@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com, ferruh.yigit@intel.com,
Radu Nicolau <radu.nicolau@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] net/iavf: fix build error
Date: Fri, 29 Oct 2021 12:14:23 +0100 [thread overview]
Message-ID: <20211029111423.2924947-2-radu.nicolau@intel.com> (raw)
In-Reply-To: <20211029111423.2924947-1-radu.nicolau@intel.com>
Fix build error and wrong parameter used for function call
Fixes: 7dd3f3e43732 ("net/iavf: add iAVF IPsec inline crypto support")
Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
---
drivers/net/iavf/iavf_ipsec_crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/iavf/iavf_ipsec_crypto.c b/drivers/net/iavf/iavf_ipsec_crypto.c
index a8022f8ed7..19e703e689 100644
--- a/drivers/net/iavf/iavf_ipsec_crypto.c
+++ b/drivers/net/iavf/iavf_ipsec_crypto.c
@@ -613,7 +613,7 @@ set_session_parameter(struct iavf_security_ctx *iavf_sctx,
} else if (conf->crypto_xform->type == RTE_CRYPTO_SYM_XFORM_AUTH) {
if (conf->crypto_xform->auth.algo == RTE_CRYPTO_AUTH_AES_GMAC) {
sess->block_sz = get_auth_blocksize(iavf_sctx,
- (enum rte_crypto_auth_algorithm)RTE_CRYPTO_SYM_XFORM_AUTH);
+ conf->crypto_xform->auth.algo);
sess->iv_sz = conf->crypto_xform->auth.iv.length;
sess->icv_sz = conf->crypto_xform->auth.digest_length;
} else {
--
2.25.1
next prev parent reply other threads:[~2021-10-29 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 11:14 [dpdk-dev] [PATCH 1/2] net/iavf: fix build error Radu Nicolau
2021-10-29 11:14 ` Radu Nicolau [this message]
2021-10-29 13:19 ` [dpdk-dev] [PATCH 2/2] " Ferruh Yigit
2021-10-29 13:19 ` [dpdk-dev] [PATCH 1/2] " Ferruh Yigit
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=20211029111423.2924947-2-radu.nicolau@intel.com \
--to=radu.nicolau@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.