From: Olivier MATZ <olivier.matz@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix empty struct rte_eth_txmode
Date: Wed, 12 Jun 2013 16:46:10 +0200 [thread overview]
Message-ID: <51B889B2.9050105@6wind.com> (raw)
In-Reply-To: <1371047405-29432-1-git-send-email-thomas.monjalon@6wind.com>
On 06/12/2013 04:30 PM, Thomas Monjalon wrote:
> The previous fix was for g++ but is broken with gcc:
> error: flexible array member in otherwise empty struct
> See http://gcc.gnu.org/onlinedocs/gcc-4.2.2/gcc/Zero-Length.html
>
> Let's fix it with #ifdef __cplusplus.
Sorry Thomas for the previous one, I should have tested it.
This one looks good, I checked compilation and it works with
gcc-4.6.3 and g++-4.6.3
next prev parent reply other threads:[~2013-06-12 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 12:23 [dpdk-dev] Can the empty struct rte_eth_txmode be enhanced? lxu
2013-06-12 13:39 ` Thomas Monjalon
2013-06-12 14:30 ` [dpdk-dev] [PATCH] ethdev: fix empty struct rte_eth_txmode Thomas Monjalon
2013-06-12 14:46 ` Olivier MATZ [this message]
2013-06-12 15:14 ` 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=51B889B2.9050105@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).