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 C1A1058CB for ; Wed, 31 May 2017 18:17:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5F43F207CD; Wed, 31 May 2017 12:17:34 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 31 May 2017 12:17:34 -0400 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:x-sasl-enc; s=mesmtp; bh=DQRD/dTWT48on/5 e1C5wNyfmsjTv4Tx/fbaJTxrPrd8=; b=hX/XZpuSE0iC3AJzJWUn+RS2FHLvVQt aB/+G9Aevh+Ra7NYVtfOidMyp6CyLapyJ9Ki/BR1wHDB4l8+YHmUqkNDcLKx8E2/ 3yj5enao0mkeLbfO696P83VbdrQ7wYV3P8IGzFWOz6Zq3ysTQWIUanqu41CDsu/m vBrWRgQWly1U= 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:x-sasl-enc; s= fm1; bh=DQRD/dTWT48on/5e1C5wNyfmsjTv4Tx/fbaJTxrPrd8=; b=CvenW2Y6 p+fsWcLoghE/WH2NeIZxNHv6c54OKOoR2JpDsELZijVTwcjzvQWiHCbkG9kmAfWn CKPEUMcO7OHxfHL7vHoMmtqiT8cS9/h+EEg7gqof8gO5OAKsAgxQSGhlNyztx7SW aefcYjec4xiYhKP8uDKRUJR5Ei2+zzz+l8Pz31XLMWOQC99Rp2ukP5x12TbM7GQc NkNKPWBqjASargpRcQKU7FI8QHqXw/6Vx22uFvN+gV7f/4Hw7AcxFi22yBEekyu6 OnLoedjhzMQydNqGmJ4Gmg66nnhyEQl8rQ/ll3p3Ch72GfCPlFEmObOFxJK5oQ3c s3nmgawTmyIfZw== X-ME-Sender: X-Sasl-enc: MVpnoVpxU4JVtaJNlcV33JEgi1hc0rPIiTcPe/j68rPZ 1496247454 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 03C367E993; Wed, 31 May 2017 12:17:34 -0400 (EDT) From: Thomas Monjalon To: Jerin Jacob Cc: Nipun Gupta , dev@dpdk.org, hemant.agrawal@nxp.com, harry.van.haaren@intel.com, bruce.richardson@intel.com, gage.eads@intel.com, shreyansh.jain@nxp.com Date: Wed, 31 May 2017 18:17:33 +0200 Message-ID: <7144115.T36RvbVuDZ@xps> In-Reply-To: <20170531145000.GA16388@jerin> References: <1495735671-4917-1-git-send-email-nipun.gupta@nxp.com> <20170531145000.GA16388@jerin> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 00/20] next-eventdev: NXP DPAA2 eventdev PMD 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: Wed, 31 May 2017 16:17:35 -0000 31/05/2017 16:50, Jerin Jacob: > -----Original Message----- > > Date: Thu, 25 May 2017 23:37:31 +0530 > > From: Nipun Gupta > > To: dev@dpdk.org > > CC: hemant.agrawal@nxp.com, jerin.jacob@caviumnetworks.com, > > harry.van.haaren@intel.com, bruce.richardson@intel.com, > > gage.eads@intel.com, shreyansh.jain@nxp.com, Nipun Gupta > > > > Subject: [PATCH 00/20] next-eventdev: NXP DPAA2 eventdev PMD > > X-Mailer: git-send-email 1.9.1 > > > > The following patch set adds NXP DPAA2 HW based eventdev > > implementation to the next-eventdev tree. > > > > The patchset consists of the following: > > - DPCON support required by DPAA2 eventdev > > - DPCI support in fslmc bus > > - Interrupt support in QBMAN > > - Implemetation of eventdev API's for DPAA2 > > - Documentation of DPAA2 eventdev PMD > > > > Hemant Agrawal (2): > > bus/fslmc: generic framework for mc object creation > > bus/fslmc: export qbman dqrr funcs for eventdev usages > > > > Nipun Gupta (18): > > event/dpaa2: add basic build infrastructure > > bus/fslmc: integrating dpio and dpbp to object framework > > bus/fslmc: adding basic dpcon support > > event/dpaa2: register dpcon as dpaa2 device for bus scan > > bus/fslmc: adding basic dpci support > > bus/fslmc: register dpci as dpaa2 device for bus scan > > bus/fslmc: adding cpu support in stashing config > > Thomas, > Is it OK to take bus/ related changes through eventdev-next? Yes if it is only related to eventdev. We must take care that these changes won't be needed by next-net, otherwise it must go in master branch.