[dpdk-dev] [PATCH v2 0/9] pci cleanup and blacklist rework

2016-03-22 Thread David Marchand
Hello Jan, On Wed, Mar 16, 2016 at 5:07 PM, Jan Viktorin wrote: > On Fri, 29 Jan 2016 15:49:04 +0100 > David Marchand wrote: > >> Before 2.2.0 release, while preparing for more changes in eal (and fixing >> a problem reported by Roger M. [1]), I came up with this (part of) patchset >> that

[dpdk-dev] [PATCH v2 0/9] pci cleanup and blacklist rework

2016-03-16 Thread Jan Viktorin
On Fri, 29 Jan 2016 15:49:04 +0100 David Marchand wrote: > Before 2.2.0 release, while preparing for more changes in eal (and fixing > a problem reported by Roger M. [1]), I came up with this (part of) patchset > that tries to make the pci code more compact and easier to read. Hello David,

[dpdk-dev] [PATCH v2 0/9] pci cleanup and blacklist rework

2016-02-09 Thread David Marchand
Hello Jan, On Mon, Feb 8, 2016 at 2:31 PM, Jan Viktorin wrote: > I am confused a bit. I started to review the "[PATCH 0/9] prepare for > rte_device > / rte_driver" series and then I've noticed there are 2 patch series having > "pci: > no need for dynamic tailq init" patch there. But then,

[dpdk-dev] [PATCH v2 0/9] pci cleanup and blacklist rework

2016-02-08 Thread Jan Viktorin
Hello David, I am confused a bit. I started to review the "[PATCH 0/9] prepare for rte_device / rte_driver" series and then I've noticed there are 2 patch series having "pci: no need for dynamic tailq init" patch there. But then, there is this v2 that does not have this patch. What is the right

[dpdk-dev] [PATCH v2 0/9] pci cleanup and blacklist rework

2016-01-29 Thread David Marchand
Before 2.2.0 release, while preparing for more changes in eal (and fixing a problem reported by Roger M. [1]), I came up with this (part of) patchset that tries to make the pci code more compact and easier to read. I ended up introducing some hooks in the pci layer to customize pci blacklist /