From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, marko.kovacevic@intel.com
Subject: [dpdk-dev] [PATCH] examples/fips_validation: fix build
Date: Mon, 5 Nov 2018 18:45:27 +0100 [thread overview]
Message-ID: <20181105174527.15671-1-thomas@monjalon.net> (raw)
The example was not added to the Makefile and there are some
compilation errors:
examples/fips_validation/main.c: In function ‘prepare_aead_op’:
error: control reaches end of non-void function
examples/fips_validation/main.c: In function ‘prepare_auth_op’:
error: control reaches end of non-void function
Fixes: f64adb6714e0 ("examples/fips_validation: support HMAC parsing")
Fixes: 4aaad2995e13 ("examples/fips_validation: support GCM parsing")
Cc: marko.kovacevic@intel.com
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
examples/Makefile | 1 +
examples/fips_validation/main.c | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/examples/Makefile b/examples/Makefile
index 356fcb1cd..33fe0e586 100644
--- a/examples/Makefile
+++ b/examples/Makefile
@@ -17,6 +17,7 @@ DIRS-$(CONFIG_RTE_LIBRTE_DISTRIBUTOR) += distributor
DIRS-y += ethtool
DIRS-y += exception_path
DIRS-$(CONFIG_RTE_LIBRTE_EFD) += server_node_efd
+DIRS-$(CONFIG_RTE_LIBRTE_CRYPTODEV) += fips_validation
DIRS-$(CONFIG_RTE_LIBRTE_FLOW_CLASSIFY) += flow_classify
DIRS-y += flow_filtering
DIRS-y += helloworld
diff --git a/examples/fips_validation/main.c b/examples/fips_validation/main.c
index 0a7e75fc8..85f54cbf0 100644
--- a/examples/fips_validation/main.c
+++ b/examples/fips_validation/main.c
@@ -459,6 +459,8 @@ prepare_auth_op(void)
}
rte_crypto_op_attach_sym_session(env.op, env.sess);
+
+ return 0;
}
static int
@@ -526,6 +528,8 @@ prepare_aead_op(void)
}
rte_crypto_op_attach_sym_session(env.op, env.sess);
+
+ return 0;
}
static int
--
2.19.0
next reply other threads:[~2018-11-05 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 17:45 Thomas Monjalon [this message]
2018-11-05 17:51 ` Ferruh Yigit
2018-11-05 20:06 ` 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=20181105174527.15671-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=marko.kovacevic@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 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).