From: Declan Doherty <declan.doherty@intel.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] cryptodev: fix icc build
Date: Wed, 12 Jul 2017 11:09:39 +0100 [thread overview]
Message-ID: <a9bd55f0-8622-1cba-5367-3301d0d51bb7@intel.com> (raw)
In-Reply-To: <20170710025923.66395-1-pablo.de.lara.guarch@intel.com>
On 10/07/17 03:59, Pablo de Lara wrote:
> Removed unnecessary macro RTE_STD_C11, which is used
> for unnamed structs.
> Since there is no longer an unnamed structure in
> rte_cryptodev_sym_session, this is not needed and
> it is actually breaking compilation on icc:
>
> lib/librte_cryptodev/rte_cryptodev.h(887): error: expected a declaration
> __extension__ void *sess_private_data[0];
> ^
> Fixes: 7c110ce7aa4e ("cryptodev: remove mempool from session")
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
...
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-07-12 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 2:59 Pablo de Lara
2017-07-12 10:09 ` Declan Doherty [this message]
2017-07-12 12:42 ` 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=a9bd55f0-8622-1cba-5367-3301d0d51bb7@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--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 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).