[PATCH v2 0/2] block: Use pci_enable_msix_exact() instead of pci_enable_msix()

From: Alexander Gordeev
Date: Wed Feb 26 2014 - 04:02:16 EST


Changes since v1:
- cciss: patch #1: a weird 'goto' removed;
- cciss: patch #2: pci_enable_msix_exact() used, not pci_enable_msix_range();
- rsxx: patch dropped - no need to change anything;

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.

This change updates 'cciss' only, but there is also 'nvme' update
pending - I am waiting for Intel guys to clarify if they want to
route it thru their tree. If not, I will post the 'nvme' patch as
a follow-up to this series.

Thanks!

Cc: Jens Axboe <axboe@xxxxxxxxx>
Cc: Mike Miller <mike.miller@xxxxxx>
Cc: iss_storagedev@xxxxxx
Cc: linux-pci@xxxxxxxxxxxxxxx

Alexander Gordeev (2):
cciss: Fallback to MSI rather than to INTx if MSI-X failed
cciss: Use pci_enable_msix_exact() instead of pci_enable_msix()

drivers/block/cciss.c | 8 +-------
1 files changed, 1 insertions(+), 7 deletions(-)

--
1.7.7.6

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/