From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Cc: marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/fips_validation: fix build
Date: Mon, 5 Nov 2018 17:51:41 +0000 [thread overview]
Message-ID: <8442ca09-3363-d637-76be-3e896a275a2d@intel.com> (raw)
In-Reply-To: <20181105174527.15671-1-thomas@monjalon.net>
On 11/5/2018 5:45 PM, Thomas Monjalon wrote:
> 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>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-11-05 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 17:45 Thomas Monjalon
2018-11-05 17:51 ` Ferruh Yigit [this message]
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=8442ca09-3363-d637-76be-3e896a275a2d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).