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
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,
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,
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
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 /
5 matches
Mail list logo