[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1389103215.git.agordeev@redhat.com>
Date: Tue, 7 Jan 2014 19:05:35 +0100
From: Alexander Gordeev <agordeev@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: Alexander Gordeev <agordeev@...hat.com>,
Brian King <brking@...ibm.com>, Tejun Heo <tj@...nel.org>,
Matthew Wilcox <willy@...ux.intel.com>,
Alex Williamson <alex.williamson@...hat.com>,
Kalle Valo <kvalo@....qualcomm.com>,
Vladimir Kondratiev <qca_vkondrat@....qualcomm.com>,
linux-wireless@...r.kernel.org, wil6210@....qualcomm.com,
ath10k@...ts.infradead.org, linux-nvme@...ts.infradead.org,
linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org,
kvm@...r.kernel.org, linux-pci@...r.kernel.org
Subject: [PATCH 0/7] Phase out pci_enable_msi_block()
As result of recent deprecation of MSI-X/MSI enablement
interfaces pci_enable_msi_block(), pci_enable_msi() and
pci_enable_msix() all drivers need to be updated to use
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
This is the first in a series of updates, to phase out
pci_enable_msi_block() function.
This series is against pci/msi branch in Bjorn Helgaas's repo:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
Thanks!
Alexander Gordeev (7):
ipr: Do not call pci_disable_msi/msix() if pci_enable_msi/msix()
failed
ipr: Use new interfaces for MSI/MSI-X enablement
ahci: Use new interfaces for MSI/MSI-X enablement
nvme: Use new interfaces for MSI/MSI-X enablement
vfio: Use new interfaces for MSI/MSI-X enablement
ath10k: Use new interfaces for MSI enablement
wil6210: Use new interfaces for MSI enablement
drivers/ata/ahci.c | 15 +++-----
drivers/block/nvme-core.c | 33 ++++-------------
drivers/net/wireless/ath/ath10k/pci.c | 22 ++++++------
drivers/net/wireless/ath/wil6210/pcie_bus.c | 36 ++++++++++---------
drivers/scsi/ipr.c | 51 +++++++++-----------------
drivers/vfio/pci/vfio_pci_intrs.c | 8 ++--
6 files changed, 66 insertions(+), 99 deletions(-)
--
1.7.7.6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists