Messages in this thread | | | Date | Mon, 21 Apr 2014 14:36:05 +0100 | From | Alexander Gordeev <> | Subject | Re: [PATCH v2] ioat: Use pci_enable_msix_exact() instead of pci_enable_msix() |
| |
On Fri, Mar 07, 2014 at 08:49:32AM +0100, 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() > 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. > > Signed-off-by: Alexander Gordeev <agordeev@redhat.com> > Cc: Dan Williams <dan.j.williams@intel.com> > Cc: Vinod Koul <vinod.koul@intel.com> > Cc: dmaengine@vger.kernel.org > Cc: linux-pci@vger.kernel.org > Acked-by: Dan Williams <dan.j.williams@intel.com>
Hi Dan,
Would you pick this patch, please?
Thanks!
-- Regards, Alexander Gordeev agordeev@redhat.com
| |