From: fengchengwen <fengchengwen@huawei.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"vladimir.medvedkin@intel.com" <vladimir.medvedkin@intel.com>,
"viktorin@rehivetech.com" <viktorin@rehivetech.com>,
"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] lpm/arm: fix SVE compile error with gcc8.3
Date: Thu, 20 May 2021 19:45:10 +0800 [thread overview]
Message-ID: <0a2fc7e1-148f-b010-02bc-aba3a01c3352@huawei.com> (raw)
In-Reply-To: <AM5PR0802MB246542B1A8C139651A53B7879E2A9@AM5PR0802MB2465.eurprd08.prod.outlook.com>
Fix in v2, thanks
On 2021/5/20 16:17, Ruifeng Wang wrote:
> Thanks for this patch.
> Minor comment below.
>
>> -----Original Message-----
>> From: Chengwen Feng <fengchengwen@huawei.com>
>> Sent: Thursday, May 20, 2021 3:17 PM
>> To: thomas@monjalon.net; ferruh.yigit@intel.com
>> Cc: dev@dpdk.org; bruce.richardson@intel.com;
>> vladimir.medvedkin@intel.com; viktorin@rehivetech.com; Ruifeng Wang
>> <Ruifeng.Wang@arm.com>; jerinj@marvell.com
>> Subject: [PATCH] lpm/arm: fix SVE compile error with gcc8.3
> This is build fix and not specific to lpm.
> Use 'build:' instead of 'lpm/arm:'?
>
next prev parent reply other threads:[~2021-05-20 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 7:16 Chengwen Feng
2021-05-20 8:17 ` Ruifeng Wang
2021-05-20 11:45 ` fengchengwen [this message]
2021-05-20 11:40 ` [dpdk-dev] [PATCH v2] build: " Chengwen Feng
2021-05-20 13:09 ` Bruce Richardson
2021-05-21 1:57 ` fengchengwen
2021-05-21 1:53 ` [dpdk-dev] [PATCH v3] " Chengwen Feng
2021-05-25 6:02 ` Ruifeng Wang
2021-05-27 7:12 ` Fengchengwen
2021-06-12 7:07 ` fengchengwen
2021-06-21 0:56 ` fengchengwen
2021-06-23 8:05 ` 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=0a2fc7e1-148f-b010-02bc-aba3a01c3352@huawei.com \
--to=fengchengwen@huawei.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=nd@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).