From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id E5AB991 for ; Mon, 19 Nov 2018 01:37:41 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 76A6621BEB; Sun, 18 Nov 2018 19:37:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 18 Nov 2018 19:37:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=O54Wu2X6v30mx+cha86HRmZhy/smzSP89Lj9DC/vfAc=; b=fqcYK/+gjQPe 1Dib1SDTuy673bOcf15u4f7NlszuVS7H3+GIKlTRT2WrndSv1s4bfwK+2ilaXEc7 amPy9IneCRziN9pLZ+JD3a58T9fYEFQYd8Umj6xdx6F+IeUjg6Gyfd3roUPn2bQt yaUYco0L26FjthdCz8+t11UoztX0gtE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=O54Wu2X6v30mx+cha86HRmZhy/smzSP89Lj9DC/vf Ac=; b=ULSGuF9LADoLL+InIcMSXPhULG8n99vZtS20XStRgV/f0urQf82YjHdam nI3uKD/L/Dt6lyckZUnwlQLfT1GrL+8Hxoni4EMdj7J5x/EQ051SWPsIz347iJbf KLzYRWCsfKqxINLud1izL1H5Sqn+jeGCcOX/1drYJNGoLdElM6LNYruoGPZgtAtr HqI13ScL8gtImNGjyhK/YNTU5zVRL9LICi3DQOlFQRi2lMjSBOZBkHXuiU4qVFVj LzMiTYeJ5JB1bPQtQ6psVX99ZBJoMIvOjRkUXK+0Ps1cO5p5B9K8u2CUFOsjAIX+ 4LcmPVSvkPq4XBtwQbgIeSGSIy2rA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3228EE4750; Sun, 18 Nov 2018 19:37:40 -0500 (EST) From: Thomas Monjalon To: Reshma Pattan Cc: dev@dpdk.org, longtb5@viettel.com.vn, john.mcnamara@intel.com Date: Mon, 19 Nov 2018 01:37:39 +0100 Message-ID: <2473532.83oZ9KRiyE@xps> In-Reply-To: <1538655839-32339-1-git-send-email-reshma.pattan@intel.com> References: <1538655839-32339-1-git-send-email-reshma.pattan@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: update timestamp validity for latency measurement X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2018 00:37:42 -0000 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 > Signed-off-by: Reshma Pattan > --- > 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