From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 201542904 for ; Tue, 16 Jan 2018 11:32:59 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8665720471; Tue, 16 Jan 2018 05:32:58 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 16 Jan 2018 05:32:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=N69fFmeU4CQ2u3L5ZLZcPh/xjv 2HJWy1nmdpUd3qAuQ=; b=FRi6iUzmjkBvvWJCjghVR1lvFinhSar28m708k5Dr7 22YG4yewKV0XCR3XvdaWgdGpVlncDGhN7zaZSaAwYQCs9FBnTl+hLTF2Xz7LGxI3 MgLxgHGpbuZOEM72QpgHLBkEHNmfsn7DYH6ljs5VZm/1rQ0fh8K3LJuyH0MPEee7 8= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=N69fFm eU4CQ2u3L5ZLZcPh/xjv2HJWy1nmdpUd3qAuQ=; b=sfL7fOf0pkr1YJJWKRnHJA C4XL3EMdon4iy5rgWSWexfzTs/+KqTZiAEUWZAcVtbauFN8AdxdYFZravbg6enYs uulFC+bs4frQG526JSZqXInzCN7my3n/44ehmGK+Gcm8mO3by6bMaixRJcrmrWhQ NKuzVbUyVgPygrSYMt+Q0WQqrUa2FI4ro80O58dqTPSDmLsb9ZkppcCmtgIq0Ipr 7YhjRnqTIwdfQRrXCRtqfig11RcpbRS35LWTlRiijLVpjL6cUG5Dc5+p0O4tLxYv iCbRWGAuIsIgWQXcuazIvLrh9b4+09qqZn47M0Yz7FuO9LGKsk56AtK2+4d+eoNg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 2AD017E353; Tue, 16 Jan 2018 05:32:58 -0500 (EST) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, hemant.agrawal@nxp.com, fiona.trahe@intel.com, rosen.xu@intel.com Date: Tue, 16 Jan 2018 11:32:26 +0100 Message-ID: <1927470.WSaafuFpEb@xps> In-Reply-To: References: <20180102125749.2379-1-shreyansh.jain@nxp.com> <2256187.Km34roPN7u@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 5/5] test: support for rawdev testcases 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: Tue, 16 Jan 2018 10:32:59 -0000 16/01/2018 11:07, Shreyansh Jain: > On Monday 15 January 2018 04:28 AM, Thomas Monjalon wrote: > > 02/01/2018 13:57, Shreyansh Jain: > >> Patch introduces rawdev unit testcase for validation against the > >> Skeleton rawdev dummy PMD implementation. > >> > >> Signed-off-by: Shreyansh Jain > >> --- > >> test/test/Makefile | 4 + > >> test/test/test_rawdev.c | 376 ++++++++++++++++++++++++++++++++++++++++++++++++ > >> 2 files changed, 380 insertions(+) > > > > As it is being done for test_eventdev_octeontx.c, I think it is > > a good idea to move the PMD unit tests in the PMD directory. > > Please check the patches from Pavan, applied in dpdk-next-eventdev. > > > > > > I saw the changes done by Pavan in eventdev-next. > > Issue I see here is that rte_test.h is currently in eventdev tree. That > would mean either I don't use those macros, or use it with this series > as dependency on master absorbing eventdev-next in near rc. > > I am assuming that post rc1 rte_test.h would be in master and thus it > would be OK to apply this series over it during rc2. Is it OK with you? Yes, you can assume next-eventdev will be pulled in master.