From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: fix C11 extensions in exported header
Date: Fri, 4 Aug 2017 13:37:49 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA8A7C0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <55d8f7ef02866b9ab921656e9e9e4a43d09f3c50.1501847638.git.adrien.mazarguil@6wind.com>
> -----Original Message-----
> From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com]
> Sent: Friday, August 4, 2017 12:56 PM
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: [PATCH 1/2] ethdev: fix C11 extensions in exported header
>
> Fix issues reported by check-includes.sh:
>
> rte_tm.h:473:2: error: anonymous unions are a C11 extension
> [-Werror,-Wc11-extensions]
> rte_tm.h:696:2: error: anonymous unions are a C11 extension
> [-Werror,-Wc11-extensions]
> rte_tm.h:904:2: error: anonymous unions are a C11 extension
> [-Werror,-Wc11-extensions]
>
> Fixes: 5d109deffa87 ("ethdev: add traffic management API")
> Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
>
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> ---
Acked-by: Cristian Dumitrescu <Cristian.Dumitrescu@intel.com>
next prev parent reply other threads:[~2017-08-04 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 11:56 Adrien Mazarguil
2017-08-04 11:56 ` [dpdk-dev] [PATCH 2/2] cryptodev: " Adrien Mazarguil
2017-08-04 12:41 ` De Lara Guarch, Pablo
2017-08-04 13:37 ` Dumitrescu, Cristian [this message]
2017-08-04 23:16 ` [dpdk-dev] [PATCH 1/2] ethdev: " 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=3EB4FA525960D640B5BDFFD6A3D891267BA8A7C0@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--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).