From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
Cc: gowrishankar.m@linux.vnet.ibm.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 1/2] net/mlx5: fix clang compilation
Date: Thu, 31 Aug 2017 16:33:44 +0100 [thread overview]
Message-ID: <bf792c80-8fed-a9b2-5e1b-e02ca2064c02@intel.com> (raw)
In-Reply-To: <7b005e17d5b2a1221e6d7237e3d36fea57a33c6a.1504104367.git.nelio.laranjeiro@6wind.com>
On 8/30/2017 3:47 PM, Nelio Laranjeiro wrote:
> On redhat 7.2 clang reports the following error:
> CC mlx5_rxmode.o
> /drivers/net/mlx5/mlx5_ethdev.c:820:32: error: field 'edata' with variable
> sized type 'struct ethtool_link_settings' not at the end of a struct or
> class is a GNU extension [-Werror,-Wgnu-variable-sized-type-not-at-end]
> struct ethtool_link_settings edata;
>
> Use alternative approach to reserve buffer space on the stack.
>
> Fixes: ef09a7fc7620 ("net/mlx5: fix inconsistent link status query")
> Cc: gowrishankar.m@linux.vnet.ibm.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Series applied to dpdk-next-net/master, thanks.
(replaced the previous version of the set on next-net)
next prev parent reply other threads:[~2017-08-31 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 15:35 [dpdk-stable] [PATCH " Nelio Laranjeiro
2017-08-29 15:35 ` [dpdk-stable] [PATCH 2/2] net/mlx5: improve stack usage during link update Nelio Laranjeiro
2017-08-30 13:56 ` [dpdk-stable] [PATCH 1/2] net/mlx5: fix clang compilation Ferruh Yigit
2017-08-30 14:47 ` [dpdk-stable] [PATCH v2 " Nelio Laranjeiro
2017-08-31 15:33 ` Ferruh Yigit [this message]
2017-08-30 14:47 ` [dpdk-stable] [PATCH v2 2/2] net/mlx5: improve stack usage during link update Nelio Laranjeiro
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=bf792c80-8fed-a9b2-5e1b-e02ca2064c02@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=nelio.laranjeiro@6wind.com \
--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).