All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Huichao Cai <chcchc88@163.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] ip_frag: add IPv4 options fragment and unit test data
Date: Fri, 11 Feb 2022 10:11:45 +0000	[thread overview]
Message-ID: <89c929d0-b49c-abbe-95af-5edf1415ce14@intel.com> (raw)
In-Reply-To: <2e09be4e.c1b.17ee69529b1.Coremail.chcchc88@163.com>

On 2/11/2022 2:20 AM, Huichao Cai wrote:
> A small problem.Why is the content of the email just sent to you not visible at Patchwork (this patch).
> 
> 

Hi Huichao,

The discussion is not in the same email thread, it looks like it spread
into multiple threads.
This is because some email headers (References:, In-Reply-To:) are dropped
by some emails (email clients?) causing reply seen as a new thread.

Because of this missing email header, I think patchwork can't relate
discussion to original patch/thread.

for record patchwork:
https://patches.dpdk.org/project/dpdk/patch/1637743626-70632-1-git-send-email-chcchc88@163.com/

  reply	other threads:[~2022-02-11 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 12:21 [PATCH] ip_frag: add IPv4 options fragment and unit test data Ananyev, Konstantin
2022-02-11  2:12 ` Huichao Cai
2022-02-11  9:41   ` Ananyev, Konstantin
2022-02-11 10:00     ` Huichao Cai
2022-02-11  2:20 ` Huichao Cai
2022-02-11 10:11   ` Ferruh Yigit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-02  9:35 Dariusz Sosnowski
2021-11-24  8:47 Huichao Cai
2021-12-01 11:49 ` Dariusz Sosnowski

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=89c929d0-b49c-abbe-95af-5edf1415ce14@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=chcchc88@163.com \
    --cc=dev@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.