From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 00/20] next-eventdev: NXP DPAA2 eventdev PMD
Date: Wed, 31 May 2017 18:17:33 +0200
Message-ID: <7144115.T36RvbVuDZ@xps>
References: <1495735671-4917-1-git-send-email-nipun.gupta@nxp.com>
 <20170531145000.GA16388@jerin>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Nipun Gupta <nipun.gupta@nxp.com>, dev@dpdk.org, hemant.agrawal@nxp.com,
 harry.van.haaren@intel.com, bruce.richardson@intel.com, gage.eads@intel.com,
 shreyansh.jain@nxp.com
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id C1A1058CB
 for <dev@dpdk.org>; Wed, 31 May 2017 18:17:34 +0200 (CEST)
In-Reply-To: <20170531145000.GA16388@jerin>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

31/05/2017 16:50, Jerin Jacob:
> -----Original Message-----
> > Date: Thu, 25 May 2017 23:37:31 +0530
> > From: Nipun Gupta <nipun.gupta@nxp.com>
> > 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
> >  <nipun.gupta@nxp.com>
> > 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.