On Mon, Aug 11, 2014 at 01:14:54PM -0400, James Smart wrote:
Alexander,
I haven't looked too deeply, but it's clear it doesn't jive with what we've
discussed in the past. Your original patches missed several other similar
sections for revision. I had sent a revised set of patches.
I was
On Sat, Jul 26, 2014 at 09:22:27AM +0100, Alexander Gordeev wrote:
On Wed, Jul 16, 2014 at 08:05:16PM +0200, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be
Alexander,
I haven't looked too deeply, but it's clear it doesn't jive with what
we've discussed in the past. Your original patches missed several other
similar sections for revision. I had sent a revised set of patches.
I was also unclear as to the merge path the patches were taking, as it
On Wed, Jul 16, 2014 at 08:05:16PM +0200, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
6 matches
Mail list logo