From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>, dev@dpdk.org
Cc: bluca@debian.org, luoxianjun@huawei.com, luoxingyu@huawei.com,
zhouguoyang@huawei.com, shahar.belkar@huawei.com,
yin.yinshi@huawei.com, david.yangxiaoliang@huawei.com,
zhaohui8@huawei.com, zhengjingzhou@huawei.com
Subject: Re: [dpdk-dev] [PATCH v5 4/4] net/hinic/base: support ipv6 flow rules
Date: Mon, 11 May 2020 21:12:18 +0100 [thread overview]
Message-ID: <40fe1ae5-7527-7947-2d60-33d3b634c3ce@intel.com> (raw)
In-Reply-To: <26d8686983a2e5397efced3c9c7f8b69f63b0b0e.1588991713.git.cloud.wangxiaoyun@huawei.com>
On 5/9/2020 5:04 AM, Xiaoyun wang wrote:
> The patch supports ipv6 flow rules for BGP or ICMP packets.
>
> Signed-off-by: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>
> ---
> drivers/net/hinic/hinic_pmd_ethdev.h | 57 +++++++++-
> drivers/net/hinic/hinic_pmd_flow.c | 209 ++++++++++++++++++++++++++++++++---
> 2 files changed, 249 insertions(+), 17 deletions(-)
>
This patchset is not changing any 'base' file, will update the patch title as
'net/hinic: ..." while merging.
next prev parent reply other threads:[~2020-05-11 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 4:04 [dpdk-dev] [PATCH v5 0/4] Support " Xiaoyun wang
2020-05-09 4:04 ` [dpdk-dev] [PATCH v5 1/4] net/hinic: increase Tx/Rx queues non-null judgment Xiaoyun wang
2020-05-11 19:09 ` Ferruh Yigit
2020-05-09 4:04 ` [dpdk-dev] [PATCH v5 2/4] net/hinic: add jumbo frame offload flag Xiaoyun wang
2020-05-09 4:04 ` [dpdk-dev] [PATCH v5 3/4] net/hinic: increase judgment for support NIC or not Xiaoyun wang
2020-05-09 4:04 ` [dpdk-dev] [PATCH v5 4/4] net/hinic/base: support ipv6 flow rules Xiaoyun wang
2020-05-11 20:12 ` Ferruh Yigit [this message]
2020-05-11 19:04 ` [dpdk-dev] [PATCH v5 0/4] Support " Ferruh Yigit
2020-05-11 20:20 ` 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=40fe1ae5-7527-7947-2d60-33d3b634c3ce@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bluca@debian.org \
--cc=cloud.wangxiaoyun@huawei.com \
--cc=david.yangxiaoliang@huawei.com \
--cc=dev@dpdk.org \
--cc=luoxianjun@huawei.com \
--cc=luoxingyu@huawei.com \
--cc=shahar.belkar@huawei.com \
--cc=yin.yinshi@huawei.com \
--cc=zhaohui8@huawei.com \
--cc=zhengjingzhou@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).