On Fri, Jan 13, 2017 at 10:57 AM, Jerin Jacob < jerin.ja...@caviumnetworks.com> wrote:
> On Fri, Jan 13, 2017 at 10:49:15AM +0000, Alejandro Lucero wrote: > > Thanks for that repo. It really makes things easier. > > > > I have run our NFP PMD unit tests using that repo, and this change seems > to > > work without no problem. > > > > Thanks again. > > Thanks Alejandro. Can I add you Acked by on your NFP PMD specific > change.i.e only for this patch([PATCH v3 25/29] net/nfp: use eal I/O > device memory read/write API) > > Sure. Thanks! > > > > > > > > On Thu, Jan 12, 2017 at 1:40 PM, Jerin Jacob < > jerin.ja...@caviumnetworks.com > > > wrote: > > > > > On Thu, Jan 12, 2017 at 10:53:17AM +0000, Alejandro Lucero wrote: > > > > Hi, > > > > > > > > I've tried to find out which dpdk repo should I use for testing this > > > change > > > > with NFP PMD. > > > > > > > > It seems rte_read/write functions are not with last dpdk main repo, > nor > > > > with dpdk-net-next. > > > > > > > > Can someone tell me which repo should I use? > > > > > > It is based on the dpdk main repo. This patchset has 29 patches. The > > > initial > > > patches in the series contains the definition of rte_read/write. > > > > > > I have created a temporary branch in public repo to make other users to > > > test the changes without applying all patches. > > > > > > https://github.com/jerinjacobk/dpdk.git > > > branch: rte_io_v3 > > > It is based on today's dpdk master and this patchset. > > > > > > >