Re: [dpdk-dev] [PATCH 00/20] next-eventdev: NXP DPAA2 eventdev PMD

[Thomas Monjalon <thomas@monjalon.net>]

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.