From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomasm@mellanox.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix compilation issue for some architectures
Date: Tue, 29 Jan 2019 05:37:23 +0000 [thread overview]
Message-ID: <AM0PR0502MB379551B4134057ECF5ACA4AFC3970@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1548685334-17260-1-git-send-email-viacheslavo@mellanox.com>
Monday, January 28, 2019 4:22 PM, Viacheslav Ovsiienko:
> Cc: dev@dpdk.org
> Subject: [PATCH] net/mlx5: fix compilation issue for some architectures
>
> Added <rte_cycles.h> inclusion, was not included on some building setups
> (ARMv8).
>
> Fixes: 61fea2920403 ("net/mlx5: fix VXLAN port registration race condition")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Applied to next-net-mlx, thanks.
Ferruh, Thomas,
This patch is to fix a previous patch wrongly applied, not new fix.
Appreciate if you can push to current release.
> ---
> drivers/net/mlx5/mlx5_flow_tcf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/mlx5/mlx5_flow_tcf.c
> b/drivers/net/mlx5/mlx5_flow_tcf.c
> index e132a34..652270f 100644
> --- a/drivers/net/mlx5/mlx5_flow_tcf.c
> +++ b/drivers/net/mlx5/mlx5_flow_tcf.c
> @@ -28,6 +28,7 @@
> #include <rte_flow.h>
> #include <rte_malloc.h>
> #include <rte_common.h>
> +#include <rte_cycles.h>
>
> #include "mlx5.h"
> #include "mlx5_flow.h"
> --
> 1.8.3.1
prev parent reply other threads:[~2019-01-29 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 14:22 Viacheslav Ovsiienko
2019-01-29 5:37 ` Shahaf Shuler [this message]
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=AM0PR0502MB379551B4134057ECF5ACA4AFC3970@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomasm@mellanox.com \
--cc=viacheslavo@mellanox.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).