DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Declan Doherty <declan.doherty@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: [dpdk-dev] [PATCH 3/3] security: fix pedentic compilation
Date: Wed, 22 Nov 2017 09:10:18 +0100	[thread overview]
Message-ID: <1c3b73f0912ad4b3da8423590dc76fc83df16b80.1511338151.git.nelio.laranjeiro@6wind.com> (raw)
In-Reply-To: <2efb17c107b980d2aea8007d19bc6363e751be10.1511338151.git.nelio.laranjeiro@6wind.com>
In-Reply-To: <2efb17c107b980d2aea8007d19bc6363e751be10.1511338151.git.nelio.laranjeiro@6wind.com>

 /root/dpdk/x86_64-native-linuxapp-gcc/include/rte_security.h:229:8: error: struct has no members [-Werror=pedantic]
  struct rte_security_macsec_xform {
         ^~~~~~~~~~~~~~~~~~~~~~~~~
 /root/dpdk/x86_64-native-linuxapp-gcc/include/rte_security.h:453:3: error: struct has no members [-Werror=pedantic]
    struct {
    ^~~~~~

Fixes: c261d1431bd8 ("security: introduce security API and framework")
Cc: akhil.goyal@nxp.com
Cc: stable@dpdk.org

Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
---
 lib/librte_security/rte_security.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/lib/librte_security/rte_security.h b/lib/librte_security/rte_security.h
index 679c0a696..bcce7a189 100644
--- a/lib/librte_security/rte_security.h
+++ b/lib/librte_security/rte_security.h
@@ -228,6 +228,7 @@ struct rte_security_ipsec_xform {
  */
 struct rte_security_macsec_xform {
 	/** To be Filled */
+	int dummy;
 };
 
 /**
@@ -471,6 +472,7 @@ struct rte_security_capability {
 		/**< IPsec capability */
 		struct {
 			/* To be Filled */
+			int dummy;
 		} macsec;
 		/**< MACsec capability */
 	};
-- 
2.11.0

  parent reply	other threads:[~2017-11-22  8:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22  8:10 [dpdk-dev] [PATCH 1/3] security: fix device operation type Nelio Laranjeiro
2017-11-22  8:10 ` [dpdk-dev] [PATCH 2/3] crypto: fix pedentic compilation errors Nelio Laranjeiro
2017-11-22  9:48   ` De Lara Guarch, Pablo
2017-11-22 10:35     ` Nelio Laranjeiro
2017-11-22 13:56   ` Neil Horman
2017-11-22 14:31     ` Gaëtan Rivet
2017-11-22 16:50       ` De Lara Guarch, Pablo
2017-11-22  8:10 ` Nelio Laranjeiro [this message]
2017-11-23 10:02   ` [dpdk-dev] [PATCH v2 1/3] security: fix device operation type Nelio Laranjeiro
2017-11-24  9:33     ` Akhil Goyal
2017-11-24 12:07       ` Nelio Laranjeiro
2018-01-08  9:58         ` [dpdk-dev] [dpdk-stable] " De Lara Guarch, Pablo
2018-01-08 10:05           ` Akhil Goyal
2018-01-08 12:34     ` De Lara Guarch, Pablo
2017-11-23 10:02   ` [dpdk-dev] [PATCH v2 2/3] crypto: fix pedantic compilation errors Nelio Laranjeiro
2017-12-11 11:49     ` De Lara Guarch, Pablo
2017-12-11 12:42       ` Nelio Laranjeiro
2017-12-11 13:54         ` De Lara Guarch, Pablo
2017-12-11 14:16           ` Nelio Laranjeiro
2018-01-08 10:00             ` De Lara Guarch, Pablo
2018-01-08 12:35     ` De Lara Guarch, Pablo
2017-11-23 10:02   ` [dpdk-dev] [PATCH v2 3/3] security: fix pedantic compilation Nelio Laranjeiro
2017-11-24  9:34     ` Akhil Goyal
2018-01-08 12:35     ` [dpdk-dev] [dpdk-stable] " De Lara Guarch, Pablo

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=1c3b73f0912ad4b3da8423590dc76fc83df16b80.1511338151.git.nelio.laranjeiro@6wind.com \
    --to=nelio.laranjeiro@6wind.com \
    --cc=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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).