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() and pci_enable_msix_range()
interfaces.

Cc: Jens Axboe <[email protected]>
Cc: Mike Miller <[email protected]>
Cc: Asai Thambi S P <[email protected]>
Cc: Joshua Morris <[email protected]>
Cc: Philip Kelleher <[email protected]>
Cc: Kyungmin Park <[email protected]>
Cc: [email protected]
Cc: [email protected]

Alexander Gordeev (9):
  cciss: Fallback to MSI rather than to INTx if MSI-X failed
  cciss: Use pci_enable_msix_range() instead of pci_enable_msix()
  mtip32xx: Remove superfluous call to pci_disable_msi()
  mtip32xx: Use pci_enable_msix_range() instead of pci_enable_msix()
  rsxx: Use pci_enable_msix_range() instead of pci_enable_msix()
  skd: Fix out of array boundary access
  skd: Fix incomplete cleanup of MSI-X interrupt
  skd: Use unified access to skdev->msix_entries throughout the code
  skd: Use pci_enable_msix_range() instead of pci_enable_msix()

 drivers/block/cciss.c             |   14 +++-----
 drivers/block/mtip32xx/mtip32xx.c |    8 +++--
 drivers/block/rsxx/core.c         |    4 +-
 drivers/block/skd_main.c          |   67 +++++++++++++++----------------------
 4 files changed, 39 insertions(+), 54 deletions(-)

-- 
1.7.7.6

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

Reply via email to