DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] cryptodev: fix C11 extensions in exported header
Date: Fri,  4 Aug 2017 13:56:22 +0200	[thread overview]
Message-ID: <61d6d83aca3273eb3ed0b6b204cf0c6fb131d635.1501847638.git.adrien.mazarguil@6wind.com> (raw)
In-Reply-To: <55d8f7ef02866b9ab921656e9e9e4a43d09f3c50.1501847638.git.adrien.mazarguil@6wind.com>

Fix issues reported by check-includes.sh:

 rte_crypto_sym.h:586:3: error: anonymous structs are a C11 extension
     [-Werror,-Wc11-extensions]
 rte_crypto_sym.h:510:2: error: anonymous unions are a C11 extension
     [-Werror,-Wc11-extensions]

Fixes: b59502a5e3d0 ("cryptodev: add AEAD parameters in crypto operation")
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>

Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
---
 lib/librte_cryptodev/rte_crypto_sym.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/librte_cryptodev/rte_crypto_sym.h b/lib/librte_cryptodev/rte_crypto_sym.h
index 58a33b8..0ceaa91 100644
--- a/lib/librte_cryptodev/rte_crypto_sym.h
+++ b/lib/librte_cryptodev/rte_crypto_sym.h
@@ -507,6 +507,7 @@ struct rte_crypto_sym_op {
 		/**< Session-less API crypto operation parameters */
 	};
 
+	RTE_STD_C11
 	union {
 		struct {
 			struct {
-- 
2.1.4

  reply	other threads:[~2017-08-04 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 11:56 [dpdk-dev] [PATCH 1/2] ethdev: " Adrien Mazarguil
2017-08-04 11:56 ` Adrien Mazarguil [this message]
2017-08-04 12:41   ` [dpdk-dev] [PATCH 2/2] cryptodev: " De Lara Guarch, Pablo
2017-08-04 13:37 ` [dpdk-dev] [PATCH 1/2] ethdev: " Dumitrescu, Cristian
2017-08-04 23:16   ` 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=61d6d83aca3273eb3ed0b6b204cf0c6fb131d635.1501847638.git.adrien.mazarguil@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).