From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 474924CE4 for ; Thu, 25 Oct 2018 13:32:06 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D918321C93; Thu, 25 Oct 2018 07:32:05 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 25 Oct 2018 07:32:05 -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=UdT5iBmf7P6pEUXXlQTPiZIYj1rqgSwRDiFr6+fJ/9Q=; b=rqdcDAolugvQ 7jVv/7Kj3kEMotPTePnK4Uc4p0In9M8/u/ME+AeT9bI8MnQyKA8J4BOJPzeUgiBV P7pWZqR1S8XPG8JZBH6wnhYp340Hxq0wKqe/44mP1AUoS8CHG9afFF4qbG67DAcW Cmt0c0fx/sHI5rpPE2i0fcCM9FQK1Us= 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=UdT5iBmf7P6pEUXXlQTPiZIYj1rqgSwRDiFr6+fJ/ 9Q=; b=YHwD6+OQlnjVpkV4N0NkvYr8Hfk3iyoc19yCjbd3io0I5dgMN94NTYrmH 3+iTkCcclEioinMq2Kuks/Q/MjCkBj0dYJcWiqoveSUqy8GCJjbC8Gg5OGtq2op7 kBKGnfXbvn02FsQE37zFwQuCKL4Mr4EtruOH77sZwb5a5YEShTE+xDI/9iVGa/14 V26WhvDo7ZWoH1jO7UqFUJUcQNCyHTIsGDxdtcozFRe0ZkXmYr9lYxKqTjwBKh1F ha23KwQ0Fs82bt/hx/sNe8xCqTawe0v88RHDWsd+vS4NobOqor/wSkOYDs+EjpvW iODlpl9F/vK9V7zDb4nqNQBnE7HTg== 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 DD66AE455C; Thu, 25 Oct 2018 07:32:03 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: Ori Kam , Dekel Peled , "wenzhuo.lu@intel.com" , "jingjing.wu@intel.com" , "bernard.iremonger@intel.com" , "olivier.matz@6wind.com" , Adrien Mazarguil , "arybchenko@solarflare.com" , Shahaf Shuler , "dev@dpdk.org" Date: Thu, 25 Oct 2018 13:32:07 +0200 Message-ID: <2211689.3Us0HrgFnG@xps> In-Reply-To: <64b69095-279e-1698-a7ca-7fbbb36ee067@intel.com> References: <1540301331-51065-1-git-send-email-dekelp@mellanox.com> <64b69095-279e-1698-a7ca-7fbbb36ee067@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix metadata API and Tx insertion 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: Thu, 25 Oct 2018 11:32:06 -0000 25/10/2018 12:45, Ferruh Yigit: > On 10/24/2018 11:49 AM, Ori Kam wrote: > > From: dev On Behalf Of Dekel Peled > >> > >> Previous patch introduces the Tx metadata feature, with unnecessary > >> restrictions on data entry. > >> It also used the metadata in txonly fwd engine only. > >> > >> This fix removes the data entry restrictions on metadata item. > >> It also implements callback function to add the metadata in every > >> Tx packet, sent by any fwd engine. > >> > >> Fixes: 32eef22f0b79 ("app/testpmd: support metadata as flow rule item") > >> Cc: dekelp@mellanox.com > >> > >> --- > >> v2: > >> No change in this patch. > >> Modified other patch in series. > >> --- > >> > >> Signed-off-by: Dekel Peled > <...> > > Acked-by: Ori Kam > > Series applied to dpdk-next-net/master, thanks. > > > Thomas, > Since the patches has been fixed are in next-net, the Fixes tags will be wrong > when you pull, can you please fix them while merging? OK, no problem