From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
linuxarm@huawei.com, xavier_huwei@163.com, xavier.huwei@tom.com,
forest.zhouchang@huawei.com, Ziyang Xuan <xuanziyang2@huawei.com>,
Xiaoyun Wang <cloud.wangxiaoyun@huawei.com>,
Guoyang Zhou <zhouguoyang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove Flow Director feature from hns3.ini and hns3_vf.ini
Date: Thu, 31 Oct 2019 19:04:06 +0000 [thread overview]
Message-ID: <f8454273-9c88-6dbc-90ee-f59a2488d818@intel.com> (raw)
In-Reply-To: <74858040.4UlEM4X2WO@xps>
On 10/25/2019 12:08 PM, Thomas Monjalon wrote:
> 15/10/2019 13:11, Ferruh Yigit:
>> On 10/11/2019 3:29 AM, Wei Hu (Xavier) wrote:
>>> This patch removes deprecated feature 'Flow Director' from hns3.ini
>>> and hns3_vf.ini because the feature has been removed from the
>>> feature list in the following commit:
>>> Commit 030febb6642c ("doc: remove deprecated ethdev features")
>>>
>>> Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com>
>>> Signed-off-by: Chunsong Feng <fengchunsong@huawei.com>
>>> ---
>>> doc/guides/nics/features/hns3.ini | 1 -
>>> doc/guides/nics/features/hns3_vf.ini | 1 -
>>> 2 files changed, 2 deletions(-)
>
> Now we need to add hinic to this fix.
>
>> Indeed I am for adding that feature back to list, sent a mail for it:
>> https://mails.dpdk.org/archives/dev/2019-October/147203.html
>
> This can be a long discussion.
>
>> Will proceed with this patch based on its result.
>
> Please fix the doc and let's discuss about how to improve the doc in a second step.
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-10-31 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 2:29 Wei Hu (Xavier)
2019-10-15 11:11 ` Ferruh Yigit
2019-10-25 11:08 ` Thomas Monjalon
2019-10-31 19:04 ` Ferruh Yigit [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=f8454273-9c88-6dbc-90ee-f59a2488d818@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=dev@dpdk.org \
--cc=forest.zhouchang@huawei.com \
--cc=linuxarm@huawei.com \
--cc=thomas@monjalon.net \
--cc=xavier.huwei@huawei.com \
--cc=xavier.huwei@tom.com \
--cc=xavier_huwei@163.com \
--cc=xuanziyang2@huawei.com \
--cc=zhouguoyang@huawei.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).