DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 5/7] mlx4: fix build with mempool debug enabled
Date: Tue, 3 Mar 2015 17:02:58 +0100	[thread overview]
Message-ID: <20150303160258.GJ23569@6wind.com> (raw)
In-Reply-To: <1425396230-13379-6-git-send-email-thomas.monjalon@6wind.com>

On Tue, Mar 03, 2015 at 04:23:48PM +0100, Thomas Monjalon wrote:
> The mempool header forces error on -Wcast-qual and makes verbs.h failing.
> Let's include verbs before as a system header.
> 
> Fixes: 7fae69eeff13 ("mlx4: new poll mode driver")
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
>  lib/librte_pmd_mlx4/mlx4.c | 22 ++++++++++------------
>  1 file changed, 10 insertions(+), 12 deletions(-)
> 
> diff --git a/lib/librte_pmd_mlx4/mlx4.c b/lib/librte_pmd_mlx4/mlx4.c
> index 492cbbf..b5774c4 100644
> --- a/lib/librte_pmd_mlx4/mlx4.c
> +++ b/lib/librte_pmd_mlx4/mlx4.c
> @@ -60,6 +60,16 @@
>  #include <linux/ethtool.h>
>  #include <linux/sockios.h>
>  
> +/* Verbs header. */
> +/* ISO C doesn't support unnamed structs/unions, disabling -pedantic. */
> +#ifdef PEDANTIC
> +#pragma GCC diagnostic ignored "-pedantic"
> +#endif
> +#include <infiniband/verbs.h>
> +#ifdef PEDANTIC
> +#pragma GCC diagnostic error "-pedantic"
> +#endif
> +
>  /* DPDK headers don't like -pedantic. */
>  #ifdef PEDANTIC
>  #pragma GCC diagnostic ignored "-pedantic"
> @@ -81,18 +91,6 @@
>  #pragma GCC diagnostic error "-pedantic"
>  #endif
>  
> -/* Verbs header. */
> -/* ISO C doesn't support unnamed structs/unions, disabling -pedantic. */
> -#ifdef PEDANTIC
> -#pragma GCC diagnostic ignored "-pedantic"
> -#endif
> -
> -#include <infiniband/verbs.h>
> -
> -#ifdef PEDANTIC
> -#pragma GCC diagnostic error "-pedantic"
> -#endif
> -
>  /* Generated configuration header. */
>  #include "mlx4_autoconf.h"
>  
> -- 
> 2.2.2

Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2015-03-03 16:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 15:23 [dpdk-dev] [PATCH 0/7] fix build with " Thomas Monjalon
2015-03-03 15:23 ` [dpdk-dev] [PATCH 1/7] mempool: " Thomas Monjalon
2015-03-04  9:59   ` Olivier MATZ
2015-03-03 15:23 ` [dpdk-dev] [PATCH 2/7] fm10k: " Thomas Monjalon
2015-03-03 15:23 ` [dpdk-dev] [PATCH 3/7] virtio: fix build with mempool " Thomas Monjalon
2015-03-04  1:15   ` Ouyang, Changchun
2015-03-03 15:23 ` [dpdk-dev] [PATCH 4/7] virtio: fix build with " Thomas Monjalon
2015-03-04  1:17   ` Ouyang, Changchun
2015-03-03 15:23 ` [dpdk-dev] [PATCH 5/7] mlx4: fix build with mempool " Thomas Monjalon
2015-03-03 16:02   ` Adrien Mazarguil [this message]
2015-03-03 15:23 ` [dpdk-dev] [PATCH 6/7] mlx4: mute auto config in quiet mode Thomas Monjalon
2015-03-03 16:03   ` Adrien Mazarguil
2015-03-03 15:23 ` [dpdk-dev] [PATCH 7/7] bond: remove debug function to fix link with shared lib Thomas Monjalon
2015-03-04  9:49   ` Declan Doherty
2015-03-04 10:21 ` [dpdk-dev] [PATCH 0/7] fix build with debug enabled 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=20150303160258.GJ23569@6wind.com \
    --to=adrien.mazarguil@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).