From: Thomas Monjalon <thomas@monjalon.net>
To: yang_y_yi@163.com, jiayu.hu@intel.com
Cc: dev@dpdk.org, konstantin.ananyev@intel.com, yangyi01@inspur.com
Subject: Re: [dpdk-dev] [PATCH v1 0/8] gro: support TCP/IPv6 and UDP/IPv6 for VLAN and VXLAN
Date: Sat, 24 Jul 2021 10:48:30 +0200 [thread overview]
Message-ID: <1859433.bPDWAe3mMg@thomas> (raw)
In-Reply-To: <5952793.xi1tbUI2Ro@thomas>
24/03/2021 22:22, Thomas Monjalon:
> 21/12/2020 04:50, yang_y_yi@163.com:
> > Yi Yang (8):
> > gro: support TCP/IPv6
> > gro: support IPv4 VXLAN TCP/IPv6
> > gro: support IPv6 VXLAN TCP/IPv4
> > gro: support IPv6 VXLAN TCP/IPv6
> > gro: support UDP/IPv6
> > gro: support IPv4 VXLAN UDP/IPv6
> > gro: support IPv6 VXLAN UDP/IPv4
> > gro: support IPv6 VXLAN UDP/IPv6
>
> There was no review/activity on this thread.
> Is it abandoned?
No reply. Should I assume it can be dropped?
next prev parent reply other threads:[~2021-07-24 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 3:50 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 1/8] gro: support TCP/IPv6 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 2/8] gro: support IPv4 VXLAN TCP/IPv6 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 3/8] gro: support IPv6 VXLAN TCP/IPv4 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 4/8] gro: support IPv6 VXLAN TCP/IPv6 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 5/8] gro: support UDP/IPv6 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 6/8] gro: support IPv4 VXLAN UDP/IPv6 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 7/8] gro: support IPv6 VXLAN UDP/IPv4 yang_y_yi
2020-12-21 3:50 ` [dpdk-dev] [PATCH v1 8/8] gro: support IPv6 VXLAN UDP/IPv6 yang_y_yi
2021-03-24 21:22 ` [dpdk-dev] [PATCH v1 0/8] gro: support TCP/IPv6 and UDP/IPv6 for VLAN and VXLAN Thomas Monjalon
2021-07-24 8:48 ` Thomas Monjalon [this message]
2021-07-25 23:53 ` Hu, Jiayu
2023-06-12 2:11 ` Stephen Hemminger
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=1859433.bPDWAe3mMg@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=yang_y_yi@163.com \
--cc=yangyi01@inspur.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).