DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] mlx: fix build with -fno-common (gcc 10)
Date: Tue, 17 Mar 2020 08:34:42 +0000	[thread overview]
Message-ID: <AM0PR0502MB401926F72A8C41B49ED91296D2F60@AM0PR0502MB4019.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200210103216.1168439-1-thomas@monjalon.net>



 From:  Thomas Monjalon
> In GCC 10, -fno-common will be the default.
> There are 2 ways of solving issues:
>   - add -fcommon
>   - stop allocating variables in .h files
> 
> In this patchset, the variables are declared extern, because it is cleaner
> anyway.
> 
> 

Series-acked-by: Matan Azrad <matan@mellanox.com>
> Thomas Monjalon (3):
>   common/mlx5: split glue initialization
>   common/mlx5: fix build with -fno-common
>   net/mlx4: fix build with -fno-common
> 
>  drivers/common/mlx5/mlx5_common.c | 80 +++++++++++++++++++--------
> ----
>  drivers/common/mlx5/mlx5_glue.h   |  2 +-
>  drivers/net/mlx4/mlx4.c           |  4 ++
>  drivers/net/mlx4/mlx4_glue.h      |  2 +-
>  drivers/net/mlx4/mlx4_rxtx.h      |  2 +-
>  5 files changed, 57 insertions(+), 33 deletions(-)
> 
> --
> 2.25.0


  parent reply	other threads:[~2020-03-17  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 10:32 Thomas Monjalon
2020-02-10 10:32 ` [dpdk-dev] [PATCH 1/3] common/mlx5: split glue initialization Thomas Monjalon
2020-02-10 10:32 ` [dpdk-dev] [PATCH 2/3] common/mlx5: fix build with -fno-common Thomas Monjalon
2020-02-10 10:32 ` [dpdk-dev] [PATCH 3/3] net/mlx4: " Thomas Monjalon
2020-03-17  8:34 ` Matan Azrad [this message]
2020-04-07  0:19   ` [dpdk-dev] [PATCH 0/3] mlx: fix build with -fno-common (gcc 10) Thomas Monjalon
2020-04-07 23:06 ` [dpdk-dev] [PATCH v2 " Thomas Monjalon
2020-04-07 23:06   ` [dpdk-dev] [PATCH v2 1/3] common/mlx5: split glue initialization Thomas Monjalon
2020-04-07 23:06   ` [dpdk-dev] [PATCH v2 2/3] common/mlx5: fix build with -fno-common Thomas Monjalon
2020-04-07 23:06   ` [dpdk-dev] [PATCH v2 3/3] net/mlx4: " Thomas Monjalon
2020-04-08  0:08 ` [dpdk-dev] [PATCH v3 0/3] mlx: fix build with -fno-common (gcc 10) Thomas Monjalon
2020-04-08  0:08   ` [dpdk-dev] [PATCH v3 1/3] common/mlx5: split glue initialization Thomas Monjalon
2020-04-08  0:08   ` [dpdk-dev] [PATCH v3 2/3] common/mlx5: fix build with -fno-common Thomas Monjalon
2020-04-08  0:09   ` [dpdk-dev] [PATCH v3 3/3] net/mlx4: " Thomas Monjalon
2020-04-12 15:51   ` [dpdk-dev] [PATCH v3 0/3] mlx: fix build with -fno-common (gcc 10) Raslan Darawsheh

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=AM0PR0502MB401926F72A8C41B49ED91296D2F60@AM0PR0502MB4019.eurprd05.prod.outlook.com \
    --to=matan@mellanox.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).