ioat: Use pci_enable_msix_exact() instead of pci_enable_msix()
authorAlexander Gordeev <agordeev@redhat.com>
Thu, 6 Mar 2014 20:11:21 +0000 (21:11 +0100)
committerDan Williams <dan.j.williams@intel.com>
Thu, 10 Apr 2014 19:17:35 +0000 (12:17 -0700)
commit368da992b93eaf8861f1ef2d27bbe22c01140733
treec8d22f8bba2eef2854db1a9cdb85359406c5c3cb
parent2358b820d42a33f1d1052b438489c90a4cc8f3fc
ioat: Use pci_enable_msix_exact() instead of pci_enable_msix()

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.

Function pci_enable_msix() returns a tri-state value while
pci_enable_msi_exact() is a canonical zero/-errno variant.
The former is being phased out in favor of the latter.
In case of 'ioat' there (should be) no difference.

Cc: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
drivers/dma/ioat/dma.c