From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 86A2EA00E6 for ; Fri, 19 Apr 2019 22:56:50 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 098701BC03; Fri, 19 Apr 2019 22:56:49 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id EE9E61B9EF; Fri, 19 Apr 2019 22:56:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 72073710; Fri, 19 Apr 2019 16:56:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 19 Apr 2019 16:56:46 -0400 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=R4sUjeE9q8CSxibZTxpDQ9awPJaiEIBrvUQn5KPjUBE=; b=lLbsQ4t1jBdx KaULjoCRKt0VtWZpFdnVC+DaA5ctzpWukS+YELKmfGjlYWFzKUHVltkqVoF+5tFq sqKT57ZgSlYw2+0D765PqJEOd0UrFKPPf9VI96+nJRgBbURrg8y5j4u2MXToppSh K/wGu8iN91FQ2jqboSBKe8z377e9cD4= 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=fm2; bh=R4sUjeE9q8CSxibZTxpDQ9awPJaiEIBrvUQn5KPjU BE=; b=rNa4aFyjzH1d8zhQfD+DQZ26h3RE99UHzIgTjCil6Wqz3W8r8s0jkrpj/ FxfSaiWP2X8bg+ztlJ2hnZCDLshCRi2pVAmRWJ8eMJl1KEAJ+8kRXIB9/Nk6rUrs hAOTa9nZ8147hNzAiK5pGAQ2BTz2XjhVtcIa55DgF7SHRcD9IlXbjsMkEoUAR0M1 do42Y3Rcvx8xobExosyFfRQnuAIgjwK6dpKA7UIvouC26PS/zHPfa3v8ZjJwDO/z jWZp6IDNTiMsEE+ErWLNGXVP7OmrqXf2dXN3WrmswU5IAbi7+Z0JSH1rxYKrOGaI taBg+KeLK8r2/C1yEVGSt3vACPGag== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrfeekgdefkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 60EFAE46C1; Fri, 19 Apr 2019 16:56:44 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, Olivier Matz , stable@dpdk.org, Chas Williams <3chas3@gmail.com> Date: Fri, 19 Apr 2019 22:56:43 +0200 Message-ID: <4471693.KZBkxzcegf@xps> In-Reply-To: <20190408071649.2hywjjy557yzor4y@platinum> References: <20190402170947.8134-1-ferruh.yigit@intel.com> <20190408071649.2hywjjy557yzor4y@platinum> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] mbuf: update Tx VLAN and QinQ mbuf flags documentation 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190419205643.0CtNs7IvISOnLpmfx749lcfLpniAQZdgEvcZqa0Lltk@z> 08/04/2019 09:16, Olivier Matz: > On Tue, Apr 02, 2019 at 06:09:46PM +0100, Ferruh Yigit wrote: > > Currently PKT_TX_VLAN and PKT_TX_QINQ mbuf flags are documented as > > they are to say packet contains VLAN or QINQ information. > > > > Updating the definition as they are requests from application to > > driver to insert VLAN or double VLAN tags into packet. > > > > Fixes: dc6c911c9993 ("mbuf: use reserved space for double vlan") > > Fixes: af75078fece3 ("first public release") > > Cc: stable@dpdk.org > > > > Signed-off-by: Ferruh Yigit > > Acked-by: Olivier Matz Applied, thanks