On Fri, Apr 12, 2013 at 4:44 PM, Yinghai Lu wrote:
> First part is for_each_pci_resource support:
> Now pci device resource iteration is done via "for (i=0...)" open code.
> That make code hard to read esp when only bridge or sriov resources
> are involved.
The "for (i = 0; ...)" code *is* a bit
On Fri, Apr 12, 2013 at 4:44 PM, Yinghai Lu ying...@kernel.org wrote:
First part is for_each_pci_resource support:
Now pci device resource iteration is done via for (i=0...) open code.
That make code hard to read esp when only bridge or sriov resources
are involved.
The for (i = 0; ...) code
First part is for_each_pci_resource support:
Now pci device resource iteration is done via "for (i=0...)" open code.
That make code hard to read esp when only bridge or sriov resources
are involved.
We want to replace those open code with for_each_pci_resource() to make
the code more readable.
First part is for_each_pci_resource support:
Now pci device resource iteration is done via for (i=0...) open code.
That make code hard to read esp when only bridge or sriov resources
are involved.
We want to replace those open code with for_each_pci_resource() to make
the code more readable.
Also
4 matches
Mail list logo