From: Thomas Monjalon <thomas@monjalon.net>
To: Rasesh Mody <rmody@marvell.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, ferruh.yigit@intel.com,
jerinj@marvell.com, GR-Everest-DPDK-Dev@marvell.com
Subject: Re: [dpdk-dev] [PATCH] net/bnx2x: fix meson build failure
Date: Tue, 05 Nov 2019 19:14:34 +0100 [thread overview]
Message-ID: <1796630.RMlmoLHBJy@xps> (raw)
In-Reply-To: <20191101060228.23271-1-rmody@marvell.com>
01/11/2019 07:02, Rasesh Mody:
> Use kernel headers for __le* types to avoid potential conflicts
> resulting in redefinition errors during Linux builds. Add check
> for BSD builds.
I don't see the error with my test builds.
Please could you describe a case where it happens?
And please provide an error log.
> Fixes: 38dff79ba736 ("net/bnx2x: update HSI")
>
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
> Tested-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
> Tested-by: Gavin Hu <gavin.hu@arm.com>
> ---
> +#ifdef __FreeBSD__
Please prefer RTE_EXEC_ENV_FREEBSD
next prev parent reply other threads:[~2019-11-05 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 6:02 Rasesh Mody
2019-11-05 18:14 ` Thomas Monjalon [this message]
2019-11-06 5:45 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2019-11-06 11:02 ` Thomas Monjalon
2019-11-05 20:34 [dpdk-dev] [PATCH] " Rasesh Mody
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=1796630.RMlmoLHBJy@xps \
--to=thomas@monjalon.net \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=rmody@marvell.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).