summaryrefslogtreecommitdiffstats
path: root/drivers/dma
diff options
context:
space:
mode:
authorAlexander Gordeev <agordeev@redhat.com>2014-03-06 21:11:21 +0100
committerDan Williams <dan.j.williams@intel.com>2014-04-10 12:17:35 -0700
commit368da992b93eaf8861f1ef2d27bbe22c01140733 (patch)
treec8d22f8bba2eef2854db1a9cdb85359406c5c3cb /drivers/dma
parent2358b820d42a33f1d1052b438489c90a4cc8f3fc (diff)
downloadlinux-368da992b93eaf8861f1ef2d27bbe22c01140733.tar.gz
linux-368da992b93eaf8861f1ef2d27bbe22c01140733.tar.bz2
linux-368da992b93eaf8861f1ef2d27bbe22c01140733.zip
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>
Diffstat (limited to 'drivers/dma')
-rw-r--r--drivers/dma/ioat/dma.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/dma/ioat/dma.c b/drivers/dma/ioat/dma.c
index 4e3549a16132..b76c1485933b 100644
--- a/drivers/dma/ioat/dma.c
+++ b/drivers/dma/ioat/dma.c
@@ -947,7 +947,7 @@ msix:
for (i = 0; i < msixcnt; i++)
device->msix_entries[i].entry = i;
- err = pci_enable_msix(pdev, device->msix_entries, msixcnt);
+ err = pci_enable_msix_exact(pdev, device->msix_entries, msixcnt);
if (err)
goto msi;