From: "Huichao Cai" <chcchc88@163.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "Dariusz Sosnowski" <dsosnowski@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re:Re:RE: Re:Re: [PATCH] ip_frag: add IPv4 options fragment and unit test data
Date: Wed, 9 Feb 2022 13:50:10 +0800 (CST) [thread overview]
Message-ID: <4b2de374.16f6.17edd083908.Coremail.chcchc88@163.com> (raw)
In-Reply-To: <1e612d2.447c.17d7b0ec856.Coremail.chcchc88@163.com>
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
Hi everyone,
This patch hasn't changed status for a long time, I want to know what the current situation of this patch is?
Huichao Cai
[-- Attachment #2: Type: text/html, Size: 2313 bytes --]
prev parent reply other threads:[~2022-02-09 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 9:35 Dariusz Sosnowski
2021-12-02 11:38 ` Huichao Cai
2021-12-02 12:03 ` Ananyev, Konstantin
2021-12-02 12:11 ` Huichao Cai
2022-02-09 5:50 ` Huichao Cai [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=4b2de374.16f6.17edd083908.Coremail.chcchc88@163.com \
--to=chcchc88@163.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=konstantin.ananyev@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).