-----Original Message----- > Date: Thu, 25 May 2017 23:37:31 +0530 > From: Nipun Gupta <nipun.gu...@nxp.com> > To: dev@dpdk.org > CC: hemant.agra...@nxp.com, jerin.ja...@caviumnetworks.com, > harry.van.haa...@intel.com, bruce.richard...@intel.com, > gage.e...@intel.com, shreyansh.j...@nxp.com, Nipun Gupta > <nipun.gu...@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?
