From: fengchengwen <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <ferruh.yigit@intel.com>, <ruifeng.wang@arm.com>
Cc: <dev@dpdk.org>, <bruce.richardson@intel.com>,
<vladimir.medvedkin@intel.com>, <viktorin@rehivetech.com>,
<jerinj@marvell.com>, <Honnappa.Nagarahalli@arm.com>,
<jerinjacobk@gmail.com>, <juraj.linkes@pantheon.tech>
Subject: Re: [dpdk-dev] [PATCH 0/2] bugfix for SVE compile
Date: Fri, 2 Jul 2021 22:15:44 +0800 [thread overview]
Message-ID: <98f6695a-f8f6-4729-a5c7-9acf82b80d6c@huawei.com> (raw)
In-Reply-To: <1624849071-56826-1-git-send-email-fengchengwen@huawei.com>
Hi, Thomas
Please review this patch set, thanks.
PS: this patch set already reviewed by ARM guys, and the CI has some
errors, but it seem not related to this patch set.
On 2021/6/28 10:57, Chengwen Feng wrote:
> This patch set contains two bugfixes for SVE compile.
> Note:
> 1) Because 2/2 patch needs backport to 20.11 so we separate it.
> 2) These two patches already acked by ARM guys from previous threads.
>
> Chengwen Feng (2):
> build: fix SVE compile error with gcc8.3
> net/hns3: fix SVE code compile error with gcc8.3
>
> config/arm/meson.build | 6 ++++++
> drivers/net/hns3/hns3_rxtx.c | 2 +-
> drivers/net/hns3/meson.build | 20 +++++++++++++++++++-
> lib/eal/arm/include/rte_vect.h | 2 +-
> lib/lpm/rte_lpm.h | 2 +-
> 5 files changed, 28 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2021-07-02 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 2:57 Chengwen Feng
2021-06-28 2:57 ` [dpdk-dev] [PATCH 1/2] build: fix SVE compile error with gcc8.3 Chengwen Feng
2021-07-09 20:18 ` Thomas Monjalon
2021-06-28 2:57 ` [dpdk-dev] [PATCH 2/2] net/hns3: fix SVE code " Chengwen Feng
2021-06-28 3:33 ` Ruifeng Wang
2021-06-28 3:56 ` fengchengwen
2021-06-28 5:33 ` Ruifeng Wang
2021-07-02 14:15 ` fengchengwen [this message]
2021-07-09 20:26 ` [dpdk-dev] [PATCH 0/2] bugfix for SVE compile Thomas Monjalon
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=98f6695a-f8f6-4729-a5c7-9acf82b80d6c@huawei.com \
--to=fengchengwen@huawei.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=juraj.linkes@pantheon.tech \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.com \
--cc=vladimir.medvedkin@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).