All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, roy.fan.zhang@intel.com,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v3 3/4] crypto: use rte macro instead of direct attribute
Date: Fri, 11 Feb 2022 16:02:37 +0000	[thread overview]
Message-ID: <20220211160238.90065-4-arkadiuszx.kusztal@intel.com> (raw)
In-Reply-To: <20220211160238.90065-1-arkadiuszx.kusztal@intel.com>

This commit replaces __extension__ attribute with
RTE_STD_C11 in anonymous unions.

It makes API consistent in terms of usage of C11
feature macro.

Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
 lib/cryptodev/rte_crypto_asym.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index 58d47158de..7bdc847702 100644
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -222,7 +222,7 @@ struct rte_crypto_rsa_xform {
 
 	enum rte_crypto_rsa_priv_key_type key_type;
 
-	__extension__
+	RTE_STD_C11
 	union {
 		rte_crypto_param d;
 		/**< d - Private key exponent
@@ -408,7 +408,7 @@ struct rte_crypto_asym_xform {
 	enum rte_crypto_asym_xform_type xform_type;
 	/**< Asymmetric crypto transform */
 
-	__extension__
+	RTE_STD_C11
 	union {
 		struct rte_crypto_rsa_xform rsa;
 		/**< RSA xform parameters */
@@ -642,7 +642,7 @@ struct rte_crypto_asym_op {
 		/**< Session-less API crypto operation parameters */
 	};
 
-	__extension__
+	RTE_STD_C11
 	union {
 		struct rte_crypto_rsa_op_param rsa;
 		struct rte_crypto_mod_op_param modex;
-- 
2.13.6


  parent reply	other threads:[~2022-02-11 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 16:02 [PATCH v3 0/4] Clarify asymmetric random, add 'k' and crypto uint Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 1/4] crypto: add dsa random number k Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 2/4] crypto: clarify usage of random numbers in asym Arek Kusztal
2022-02-11 16:02 ` Arek Kusztal [this message]
2022-02-11 16:02 ` [PATCH v3 4/4] crypto: reorganize endianness comments, add crypto uint Arek Kusztal
2022-02-12 10:52 ` [EXT] [PATCH v3 0/4] Clarify asymmetric random, add 'k' and " Akhil Goyal

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=20220211160238.90065-4-arkadiuszx.kusztal@intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=roy.fan.zhang@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.