From: Fan Zhang <roy.fan.zhang@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-dev] [PATCH] examples/fips_validation: fix device start
Date: Thu, 28 Oct 2021 11:22:00 +0100 [thread overview]
Message-ID: <20211028102200.197584-1-roy.fan.zhang@intel.com> (raw)
Fixes: 261bbff75e34 ("examples: use separate crypto session mempools")
Cc: roy.fan.zhang@intel.com
Bugzilla Link: https://bugs.dpdk.org/show_bug.cgi?id=842
This patch fixes the missing device start for fips validation
sample app.
Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
---
examples/fips_validation/main.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/examples/fips_validation/main.c b/examples/fips_validation/main.c
index b0de3d269a..dc40bffe7d 100644
--- a/examples/fips_validation/main.c
+++ b/examples/fips_validation/main.c
@@ -134,6 +134,10 @@ cryptodev_fips_validate_app_int(void)
if (ret < 0)
goto error_exit;
+ ret = rte_cryptodev_start(env.dev_id);
+ if (ret < 0)
+ goto error_exit;
+
return 0;
error_exit:
--
2.25.1
next reply other threads:[~2021-10-28 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 10:22 Fan Zhang [this message]
2021-10-31 20:40 ` [dpdk-dev] [EXT] " Akhil Goyal
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=20211028102200.197584-1-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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 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).