From: Alexander Gordeev <agordeev@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Alexander Gordeev <agordeev@redhat.com>,
Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [PATCH 0/2] ib: Use pci_enable_msix_range() instead of pci_enable_msix()
Date: Tue, 18 Feb 2014 16:09:00 +0100 [thread overview]
Message-ID: <cover.1392733151.git.agordeev@redhat.com> (raw)
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: Roland Dreier <roland@kernel.org>
Cc: Sean Hefty <sean.hefty@intel.com>
Cc: Hal Rosenstock <hal.rosenstock@gmail.com>
Cc: linux-rdma@vger.kernel.org
Cc: linux-pci@vger.kernel.org
Alexander Gordeev (2):
mthca: Use pci_enable_msix_range() instead of pci_enable_msix()
qib: Use pci_enable_msix_range() instead of pci_enable_msix()
drivers/infiniband/hw/mthca/mthca_main.c | 9 ++---
drivers/infiniband/hw/qib/qib_pcie.c | 55 +++++++++++++++--------------
2 files changed, 31 insertions(+), 33 deletions(-)
--
1.7.7.6
next reply other threads:[~2014-02-18 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 15:09 Alexander Gordeev [this message]
2014-02-18 15:09 ` [PATCH 1/2] mthca: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-23 6:57 ` [PATCH v2 1/2] IB/mthca: Use pci_enable_msix_exact() " Alexander Gordeev
2014-02-18 15:09 ` [PATCH 2/2] qib: Use pci_enable_msix_range() " Alexander Gordeev
2014-02-18 16:52 ` Marciniszyn, Mike
2014-02-19 23:11 ` Marciniszyn, Mike
2014-04-09 13:22 ` Alexander Gordeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1392733151.git.agordeev@redhat.com \
--to=agordeev@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.