Re: [dpdk-dev] [PATCH 0/9] rte_bus parse API

2017-06-08 Thread Gaëtan Rivet
On Thu, Jun 08, 2017 at 01:38:12PM +0200, Jan Blunck wrote: > On Wed, Jun 7, 2017 at 9:55 PM, Gaëtan Rivet wrote: > > On Wed, Jun 07, 2017 at 07:22:05PM +0200, Jan Blunck wrote: > >> On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet > >> wrote: > >> > Following the evolutions announced in [1], here

Re: [dpdk-dev] [PATCH 0/9] rte_bus parse API

2017-06-08 Thread Jan Blunck
On Wed, Jun 7, 2017 at 9:55 PM, Gaëtan Rivet wrote: > On Wed, Jun 07, 2017 at 07:22:05PM +0200, Jan Blunck wrote: >> On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet wrote: >> > Following the evolutions announced in [1], here is the first part of >> > the rte_devargs rework planned for 17.08. The ra

Re: [dpdk-dev] [PATCH 0/9] rte_bus parse API

2017-06-07 Thread Gaëtan Rivet
On Wed, Jun 07, 2017 at 07:22:05PM +0200, Jan Blunck wrote: > On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet wrote: > > Following the evolutions announced in [1], here is the first part of > > the rte_devargs rework planned for 17.08. The rationale has been partially > > explained in [2]. > > > > T

Re: [dpdk-dev] [PATCH 0/9] rte_bus parse API

2017-06-07 Thread Jan Blunck
On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet wrote: > Following the evolutions announced in [1], here is the first part of > the rte_devargs rework planned for 17.08. The rationale has been partially > explained in [2]. > > This first part covers the introduction of the necessary facilities in >

[dpdk-dev] [PATCH 0/9] rte_bus parse API

2017-05-24 Thread Gaetan Rivet
Following the evolutions announced in [1], here is the first part of the rte_devargs rework planned for 17.08. The rationale has been partially explained in [2]. This first part covers the introduction of the necessary facilities in rte_bus to allow for generic device parsing. This API is implemen