From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Hu <gavin.hu@arm.com>
Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com, stable@dpdk.org,
Sirshak Das <sirshak.das@arm.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/3] net/mlx5: fix the clang compiling issue
Date: Mon, 21 May 2018 01:02:13 +0200 [thread overview]
Message-ID: <52655603.Nh8Pk5rl52@xps> (raw)
In-Reply-To: <20180517024610.36416-1-gavin.hu@arm.com>
17/05/2018 04:46, Gavin Hu:
> From: gavin hu <gavin.hu@arm.com>
>
> This patch adds a pair of "()" to embrace the argument
> input to the function-like macro invocation.
>
> drivers/net/mlx5/mlx5_rxtx_vec.c:37:
> drivers/net/mlx5/mlx5_rxtx_vec_neon.h:170:24: error: too many arguments
> provided to function-like macro invocation
> (uint16x8_t) { 0, 0, cs_flags,
> rte_cpu_to_be_16(len),
>
> Fixes: 570acdb1da ("net/mlx5: add vectorized Rx/Tx burst for ARM")
> Cc: stable@dpdk.org
>
> Signed-off-by: Gavin Hu <gavin.hu@arm.com>
> Signed-off-by: Sirshak Das <sirshak.das@arm.com>
> Reviewed-by: Phil Yang <Phil.Yang@arm.com>
> Reviewed-by: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Reviewed-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
Series applied, thanks
prev parent reply other threads:[~2018-05-20 23:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 8:28 [dpdk-dev] [PATCH 0/4] *** fix native clang compiling errors on ARM64 *** Gavin Hu
2018-05-15 8:28 ` [dpdk-dev] [PATCH 1/4] app: add LDFLAGS -latomic to link atomic lib Gavin Hu
2018-05-15 9:00 ` Bruce Richardson
2018-05-15 10:10 ` Gavin Hu
2018-05-15 9:07 ` Jerin Jacob
2018-05-15 8:28 ` [dpdk-dev] [PATCH 2/4] Driver/Mellanox: fix PMD compiling issue Gavin Hu
2018-05-15 9:11 ` Jerin Jacob
2018-05-15 8:28 ` [dpdk-dev] [PATCH 3/4] cryptodev: fix the clang " Gavin Hu
2018-05-15 8:28 ` [dpdk-dev] [PATCH 4/4] ifpgai_rawdev: " Gavin Hu
2018-05-15 9:23 ` [dpdk-dev] [PATCH v2 1/4] app: add LDFLAGS -latomic to link atomic lib Gavin Hu
2018-05-15 9:23 ` [dpdk-dev] [PATCH v2 2/4] Driver/Mellanox: fix PMD compiling issue Gavin Hu
2018-05-15 17:05 ` Yongseok Koh
2018-05-15 17:52 ` Sirshak Das
2018-05-15 18:38 ` Yongseok Koh
2018-05-15 9:23 ` [dpdk-dev] [PATCH v2 3/4] cryptodev: fix the clang " Gavin Hu
2018-05-15 11:41 ` Jerin Jacob
2018-05-15 13:34 ` De Lara Guarch, Pablo
2018-05-15 9:23 ` [dpdk-dev] [PATCH v2 4/4] ifpgai_rawdev: " Gavin Hu
2018-05-16 5:13 ` Jerin Jacob
2018-05-15 11:38 ` [dpdk-dev] [PATCH v2 1/4] app: add LDFLAGS -latomic to link atomic lib Jerin Jacob
2018-05-16 6:08 ` [dpdk-dev] [PATCH v3 1/3] net/mlx5: fix the clang compiling issue Gavin Hu
2018-05-16 6:08 ` [dpdk-dev] [PATCH v3 2/3] eventdev: " Gavin Hu
2018-05-16 6:08 ` [dpdk-dev] [PATCH v3 3/3] raw/ifpga_rawdev: " Gavin Hu
2018-05-16 6:45 ` Jerin Jacob
2018-05-17 1:47 ` Gavin Hu
2018-05-20 22:28 ` Thomas Monjalon
2018-05-17 2:46 ` [dpdk-dev] [PATCH v4 1/3] net/mlx5: " Gavin Hu
2018-05-17 2:46 ` [dpdk-dev] [PATCH v4 2/3] eventdev: " Gavin Hu
2018-05-17 2:46 ` [dpdk-dev] [PATCH v4 3/3] raw/ifpga: " Gavin Hu
2018-05-20 23:02 ` Thomas Monjalon [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=52655603.Nh8Pk5rl52@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=sirshak.das@arm.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).