From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: [PATCH] test/eventdev: use CPU event type Date: Sat, 9 Dec 2017 14:57:47 +0530 Message-ID: <20171209092746.GC13525@jerin> References: <20171204081118.15537-1-jerin.jacob@caviumnetworks.com> <20171204084444.7awnhs2rz2wmblt7@Pavan-LT> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Pavan Nikhilesh Bhagavatula Return-path: Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0051.outbound.protection.outlook.com [104.47.42.51]) by dpdk.org (Postfix) with ESMTP id DF0AD7CBD for ; Sat, 9 Dec 2017 10:28:12 +0100 (CET) Content-Disposition: inline In-Reply-To: <20171204084444.7awnhs2rz2wmblt7@Pavan-LT> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" -----Original Message----- > Date: Mon, 4 Dec 2017 14:14:45 +0530 > From: Pavan Nikhilesh Bhagavatula > To: Jerin Jacob > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] test/eventdev: use CPU event type > User-Agent: NeoMutt/20170609 (1.8.3) > > On Mon, Dec 04, 2017 at 01:41:18PM +0530, Jerin Jacob wrote: > > octeontx test application was using non RTE_EVENT_TYPE_CPU > > event type to generate the event from CPU. Upon the introduction > > of ethdev Rx adapter, RTE_EVENT_TYPE_ETHDEV has special > > meaning. So avoid using non RTE_EVENT_TYPE_CPU event types > > to inject events from CPU. > > > > Fixes: d0d654986018 ("net/octeontx: support event Rx adapter") > > Cc: stable@dpdk.org > > > > Signed-off-by: Jerin Jacob > > --- > > test/test/test_eventdev_octeontx.c | 6 +++--- > Reviewed-by: Pavan Nikhilesh Applied to dpdk-next-eventdev/master. Thanks.