From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 4/5] doc: update hns3 feature list
Date: Tue, 20 Apr 2021 11:34:12 +0100 [thread overview]
Message-ID: <4f531211-f98a-9d57-d9ac-b671415923a3@intel.com> (raw)
In-Reply-To: <1618909192-17431-5-git-send-email-humin29@huawei.com>
On 4/20/2021 9:59 AM, Min Hu (Connor) wrote:
> Hns3 PMD has supported SR-IOV in 19.11 version.
> This patch added feature description in hns3.ini.
>
Can you please add the commit id of the patch that adds the actual support?
It can be added as fixes tag.
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> ---
> doc/guides/nics/features/hns3.ini | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/guides/nics/features/hns3.ini b/doc/guides/nics/features/hns3.ini
> index 0f89c60..2a46dde 100644
> --- a/doc/guides/nics/features/hns3.ini
> +++ b/doc/guides/nics/features/hns3.ini
> @@ -25,6 +25,7 @@ Multicast MAC filter = Y
> RSS hash = Y
> RSS key update = Y
> RSS reta update = Y
> +SR-IOV = Y
> DCB = Y
> VLAN filter = Y
> Flow control = Y
>
next prev parent reply other threads:[~2021-04-20 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 8:59 [dpdk-dev] [PATCH 0/5] fixes for hns3 PMD Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 1/5] net/hns3: delete unused macro Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 2/5] net/hns3: fix enum variable used as boolean Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 3/5] net/hns3: fix unchecked function call Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 4/5] doc: update hns3 feature list Min Hu (Connor)
2021-04-20 10:34 ` Ferruh Yigit [this message]
2021-04-20 8:59 ` [dpdk-dev] [PATCH 5/5] doc: fix Rx burst function doc Min Hu (Connor)
2021-04-20 10:56 ` [dpdk-dev] [PATCH 0/5] fixes for hns3 PMD 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=4f531211-f98a-9d57-d9ac-b671415923a3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@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).