From: Thomas Monjalon <thomas@monjalon.net>
To: Reshma Pattan <reshma.pattan@intel.com>
Cc: dev@dpdk.org, longtb5@viettel.com.vn, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: update timestamp validity for latency measurement
Date: Mon, 19 Nov 2018 01:37:39 +0100 [thread overview]
Message-ID: <2473532.83oZ9KRiyE@xps> (raw)
In-Reply-To: <1538655839-32339-1-git-send-email-reshma.pattan@intel.com>
04/10/2018 14:23, Reshma Pattan:
> Updated the doc on how packets are marked to identify
> their timestamp as valid and considered for latency
> measurement.
>
> Suggested-by: Bao-Long Tran <longtb5@viettel.com.vn>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
> This change is relevant to the below patch and must be applied
> after that.
> http://patches.dpdk.org/patch/45328/
It's better to squash doc & code patches together, when possible.
Applied, thanks
prev parent reply other threads:[~2018-11-19 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 12:23 Reshma Pattan
2018-11-14 10:14 ` Kovacevic, Marko
2018-11-19 0:37 ` Thomas Monjalon [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=2473532.83oZ9KRiyE@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=longtb5@viettel.com.vn \
--cc=reshma.pattan@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).