From: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
To: dev@dpdk.org
Cc: jingjing.wu@intel.com, pablo.de.lara.guarch@intel.com
Subject: [PATCH 1/2] examples/l2fwd-crypto: fix for icc
Date: Mon, 4 Apr 2016 10:46:50 +0200 [thread overview]
Message-ID: <1459759611-13788-2-git-send-email-danielx.t.mrzyglod@intel.com> (raw)
In-Reply-To: <1459759611-13788-1-git-send-email-danielx.t.mrzyglod@intel.com>
Fix for compilation errors for icc:
error #188: enumerated type mixed with another type
Fixes: 00c58901f1b3 ("examples/l2fwd-crypto: use key-value list of supported algorithms")
Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
---
examples/l2fwd-crypto/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/examples/l2fwd-crypto/main.c b/examples/l2fwd-crypto/main.c
index 35171d1..182dc56 100644
--- a/examples/l2fwd-crypto/main.c
+++ b/examples/l2fwd-crypto/main.c
@@ -902,7 +902,7 @@ parse_cipher_algo(enum rte_crypto_cipher_algorithm *algo, char *optarg)
for (i = 0; i < RTE_CRYPTO_CIPHER_LIST_END; i++) {
if (!strcmp(supported_cipher_algo[i], optarg)) {
- *algo = i;
+ *algo = (enum rte_crypto_cipher_algorithm)i;
return 0;
}
}
@@ -978,7 +978,7 @@ parse_auth_algo(enum rte_crypto_auth_algorithm *algo, char *optarg)
for (i = 0; i < RTE_CRYPTO_AUTH_LIST_END; i++) {
if (!strcmp(supported_auth_algo[i], optarg)) {
- *algo = i;
+ *algo = (enum rte_crypto_auth_algorithm)i;
return 0;
}
}
--
2.5.5
next prev parent reply other threads:[~2016-04-04 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:46 [PATCH 0/2] fixes for icc build errors Daniel Mrzyglod
2016-04-04 8:46 ` Daniel Mrzyglod [this message]
2016-04-04 9:34 ` [PATCH 1/2] examples/l2fwd-crypto: fix for icc De Lara Guarch, Pablo
2016-04-04 8:46 ` [PATCH 2/2] examples: fix build errors " Daniel Mrzyglod
2016-04-04 9:33 ` De Lara Guarch, Pablo
2016-04-04 9:38 ` Mrzyglod, DanielX T
2016-04-04 10:26 ` De Lara Guarch, Pablo
2016-04-04 10:56 ` [PATCH v2] " Daniel Mrzyglod
2016-04-04 13:07 ` [PATCH 0/2] fixes for icc build errors 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=1459759611-13788-2-git-send-email-danielx.t.mrzyglod@intel.com \
--to=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=pablo.de.lara.guarch@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.