DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Cc: Akhil Goyal <gakhil@marvell.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Chengwen Feng <fengchengwen@huawei.com>,
	Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	David Hunt <david.hunt@intel.com>,
	Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>,
	Harman Kalra <hkalra@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Junfeng Guo <junfeng.guo@intel.com>,
	Kevin Laatz <kevin.laatz@intel.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	Matan Azrad <matan@nvidia.com>,
	Matt Peters <matt.peters@windriver.com>,
	Naga Harish K S V <s.v.naga.harish.k@intel.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Olivier Matz <olivier.matz@6wind.com>, Ori Kam <orika@nvidia.com>,
	Radu Nicolau <radu.nicolau@intel.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Sameh Gobriel <sameh.gobriel@intel.com>,
	Satha Rao <skoteshwar@marvell.com>, Simei Su <simei.su@intel.com>,
	Srikanth Yalavarthi <syalavarthi@marvell.com>,
	Steven Webster <steven.webster@windriver.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Yipeng Wang <yipeng1.wang@intel.com>,
	Zhirun Yan <zhirun.yan@intel.com>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH 13/32] mbuf: remove use of RTE STD C11 macro
Date: Fri, 11 Aug 2023 15:22:28 -0700	[thread overview]
Message-ID: <1691792567-10805-14-git-send-email-roretzla@linux.microsoft.com> (raw)
In-Reply-To: <1691792567-10805-1-git-send-email-roretzla@linux.microsoft.com>

C11 conformant compiler is documented as a minimum requirement to build
and consume DPDK. Remove use of RTE_STD_C11 macro marking use of C11
features with __extension__ since it is no longer necessary.

Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
---
 lib/mbuf/rte_mbuf_core.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/lib/mbuf/rte_mbuf_core.h b/lib/mbuf/rte_mbuf_core.h
index 2030b3b..e9bc0d1 100644
--- a/lib/mbuf/rte_mbuf_core.h
+++ b/lib/mbuf/rte_mbuf_core.h
@@ -522,7 +522,6 @@ struct rte_mbuf {
 	 * would have RTE_PTYPE_L2_ETHER and not RTE_PTYPE_L2_VLAN because the
 	 * vlan is stripped from the data.
 	 */
-	RTE_STD_C11
 	union {
 		uint32_t packet_type; /**< L2/L3/L4 and tunnel information. */
 		__extension__
@@ -531,7 +530,6 @@ struct rte_mbuf {
 			uint8_t l3_type:4;   /**< (Outer) L3 type. */
 			uint8_t l4_type:4;   /**< (Outer) L4 type. */
 			uint8_t tun_type:4;  /**< Tunnel type. */
-			RTE_STD_C11
 			union {
 				uint8_t inner_esp_next_proto;
 				/**< ESP next protocol type, valid if
@@ -555,7 +553,6 @@ struct rte_mbuf {
 	/** VLAN TCI (CPU order), valid if RTE_MBUF_F_RX_VLAN is set. */
 	uint16_t vlan_tci;
 
-	RTE_STD_C11
 	union {
 		union {
 			uint32_t rss;     /**< RSS hash result if RSS enabled */
@@ -614,7 +611,6 @@ struct rte_mbuf {
 #endif
 
 	/* fields to support TX offloads */
-	RTE_STD_C11
 	union {
 		uint64_t tx_offload;       /**< combined for easy fetch */
 		__extension__
-- 
1.8.3.1


  parent reply	other threads:[~2023-08-11 22:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 22:22 [PATCH 00/32] Remove use and definition of RTE_STD_C11 macro Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 01/32] timer: remove use of RTE STD C11 macro Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 02/32] stack: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 03/32] security: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 04/32] sched: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 05/32] ring: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 06/32] regexdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 07/32] rawdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 08/32] power: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 09/32] pipeline: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 10/32] net: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 11/32] mldev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 12/32] mempool: " Tyler Retzlaff
2023-08-11 22:22 ` Tyler Retzlaff [this message]
2023-08-11 22:22 ` [PATCH 14/32] ip_frag: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 15/32] hash: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 16/32] graph: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 17/32] eventdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 18/32] ethdev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 19/32] dmadev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 20/32] cryptodev: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 21/32] examples/ipsec-secgw: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 22/32] examples/ip_pipeline: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 23/32] net/sfc: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 24/32] net/octeontx: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 25/32] net/mlx5: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 26/32] net/mlx4: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 27/32] net/igc: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 28/32] net/avp: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 29/32] dma/idxd: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 30/32] common/mlx5: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 31/32] common/cnxk: " Tyler Retzlaff
2023-08-11 22:22 ` [PATCH 32/32] eal: remove use and definition " Tyler Retzlaff
2023-08-14  8:40 ` [PATCH 00/32] Remove use and definition of RTE_STD_C11 macro Bruce Richardson
2023-08-14  8:45 ` Morten Brørup
2023-08-14  8:47 ` Morten Brørup
2023-08-16 16:32 ` David Marchand
2023-08-30 17:34 ` Thomas Monjalon
2023-08-31 23:12   ` Tyler Retzlaff

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=1691792567-10805-14-git-send-email-roretzla@linux.microsoft.com \
    --to=roretzla@linux.microsoft.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=fanzhang.oss@gmail.com \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hkalra@marvell.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=junfeng.guo@intel.com \
    --cc=kevin.laatz@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=matan@nvidia.com \
    --cc=matt.peters@windriver.com \
    --cc=ndabilpuram@marvell.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@nvidia.com \
    --cc=radu.nicolau@intel.com \
    --cc=s.v.naga.harish.k@intel.com \
    --cc=sachin.saxena@nxp.com \
    --cc=sameh.gobriel@intel.com \
    --cc=simei.su@intel.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=steven.webster@windriver.com \
    --cc=suanmingm@nvidia.com \
    --cc=syalavarthi@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    --cc=vladimir.medvedkin@intel.com \
    --cc=yipeng1.wang@intel.com \
    --cc=zhirun.yan@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).