From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>,
wenzhuo.lu@intel.com, konstantin.ananyev@intel.com,
jerinj@marvell.com, viktorin@rehivetech.com
Cc: dev@dpdk.org, gavin.hu@arm.com, honnappa.nagarahalli@arm.com,
juraj.linkes@pantheon.tech, nd@arm.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/3] arch/arm: add vcopyq intrinsic for aarch32
Date: Fri, 1 May 2020 15:55:54 +0100 [thread overview]
Message-ID: <a9043100-7853-6688-213e-6d85bd93dc7c@intel.com> (raw)
In-Reply-To: <20200424065053.119885-2-ruifeng.wang@arm.com>
On 4/24/2020 7:50 AM, Ruifeng Wang wrote:
> vcopyq_laneq_u32 should be implemented for aarch32 which doesn't have
> the intrinsic.
>
> Fixes: 3c4b4024c225 ("arch/arm: add vcopyq_laneq_u32 for old gcc")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
This fixes build of examples/l3fwd for armv7.
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2020-05-01 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200424065053.119885-1-ruifeng.wang@arm.com>
2020-04-24 6:50 ` Ruifeng Wang
2020-05-01 14:55 ` Ferruh Yigit [this message]
2020-04-24 6:50 ` [dpdk-stable] [PATCH 3/3] net/ixgbe: fix include of vector header file Ruifeng Wang
[not found] ` <20200623065856.41189-1-ruifeng.wang@arm.com>
2020-06-23 6:58 ` [dpdk-stable] [PATCH v2 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-23 6:58 ` [dpdk-stable] [PATCH v2 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
[not found] ` <20200624071016.210656-1-ruifeng.wang@arm.com>
2020-06-24 7:10 ` [dpdk-stable] [PATCH v3 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-24 7:10 ` [dpdk-stable] [PATCH v3 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
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=a9043100-7853-6688-213e-6d85bd93dc7c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=juraj.linkes@pantheon.tech \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=stable@dpdk.org \
--cc=viktorin@rehivetech.com \
--cc=wenzhuo.lu@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).