From: Ruifeng Wang <ruifeng.wang@arm.com>
To: Jerin Jacob <jerinj@marvell.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Wei Zhao <wei.zhao1@intel.com>, Jeff Guo <jia.guo@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
honnappa.nagarahalli@arm.com, juraj.linkes@pantheon.tech,
nd@arm.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH v3 3/4] net/ixgbe: fix include of vector header file
Date: Wed, 24 Jun 2020 15:10:14 +0800 [thread overview]
Message-ID: <20200624071016.210656-4-ruifeng.wang@arm.com> (raw)
In-Reply-To: <20200624071016.210656-1-ruifeng.wang@arm.com>
The include of 'arm_neon.h' causes issues to old gcc and aarch32.
Including 'rte_vect.h' instead fixes these issues.
Fixes: b20971b6cca0 ("net/ixgbe: implement vector driver for ARM")
Cc: stable@dpdk.org
Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
---
drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c b/drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c
index 293b7c8bd..aa27ee177 100644
--- a/drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c
+++ b/drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c
@@ -5,13 +5,12 @@
#include <stdint.h>
#include <rte_ethdev_driver.h>
#include <rte_malloc.h>
+#include <rte_vect.h>
#include "ixgbe_ethdev.h"
#include "ixgbe_rxtx.h"
#include "ixgbe_rxtx_vec_common.h"
-#include <arm_neon.h>
-
#pragma GCC diagnostic ignored "-Wcast-qual"
static inline void
--
2.17.1
next prev parent reply other threads:[~2020-06-24 7:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 6:50 [dpdk-dev] [PATCH 0/3] aarch32 compilation Ruifeng Wang
2020-04-24 6:50 ` [dpdk-dev] [PATCH 1/3] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-05-01 14:55 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2020-04-24 6:50 ` [dpdk-dev] [PATCH 2/3] net/ixgbe: add support " Ruifeng Wang
2020-05-01 14:59 ` Ferruh Yigit
2020-05-06 7:54 ` Ruifeng Wang
2020-04-24 6:50 ` [dpdk-dev] [PATCH 3/3] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-05-01 15:06 ` [dpdk-dev] [PATCH 0/3] aarch32 compilation Ferruh Yigit
2020-05-06 8:09 ` Ruifeng Wang
2020-05-06 10:14 ` Ferruh Yigit
2020-05-06 13:54 ` Ruifeng Wang
2020-05-06 14:14 ` Ferruh Yigit
2020-05-06 14:36 ` Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 0/4] " Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-23 8:37 ` David Marchand
2020-06-23 8:59 ` Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-23 6:58 ` [dpdk-dev] [PATCH v2 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-24 7:10 ` Ruifeng Wang [this message]
2020-06-24 7:10 ` [dpdk-dev] [PATCH v3 4/4] net/i40e: " Ruifeng Wang
2020-06-26 13:44 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ferruh Yigit
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=20200624071016.210656-4-ruifeng.wang@arm.com \
--to=ruifeng.wang@arm.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=jia.guo@intel.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--cc=wei.zhao1@intel.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).