From: Bjorn Helgaas <bhelgaas@google.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 RESEND 2/4] portdrv: Use pci_enable_msix_exact() instead of pci_enable_msix()
Date: Wed, 12 Mar 2014 21:56:34 -0600 [thread overview]
Message-ID: <20140313035634.GA26657@google.com> (raw)
In-Reply-To: <b1f560f01a176784ebfff28b84574d2850413729.1394128952.git.agordeev@redhat.com>
On Thu, Mar 06, 2014 at 09:11:22PM +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.
>
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: linux-pci@vger.kernel.org
Applied to pci/msi for v3.15, thanks!
> ---
> drivers/pci/pcie/portdrv_core.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
> index 986f8ea..0b1efb2 100644
> --- a/drivers/pci/pcie/portdrv_core.c
> +++ b/drivers/pci/pcie/portdrv_core.c
> @@ -99,7 +99,7 @@ static int pcie_port_enable_msix(struct pci_dev *dev, int *vectors, int mask)
> for (i = 0; i < nr_entries; i++)
> msix_entries[i].entry = i;
>
> - status = pci_enable_msix(dev, msix_entries, nr_entries);
> + status = pci_enable_msix_exact(dev, msix_entries, nr_entries);
> if (status)
> goto Exit;
>
> @@ -171,7 +171,7 @@ static int pcie_port_enable_msix(struct pci_dev *dev, int *vectors, int mask)
> pci_disable_msix(dev);
>
> /* Now allocate the MSI-X vectors for real */
> - status = pci_enable_msix(dev, msix_entries, nvec);
> + status = pci_enable_msix_exact(dev, msix_entries, nvec);
> if (status)
> goto Exit;
> }
> --
> 1.7.7.6
>
next prev parent reply other threads:[~2014-03-13 3:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 20:11 [PATCH v2 RESEND 0/4] : Use pci_enable_msix_exact() instead of pci_enable_msix() Alexander Gordeev
2014-03-06 20:11 ` [PATCH v2 RESEND 1/4] ioat: " Alexander Gordeev
2014-03-06 21:09 ` Dan Williams
2014-03-06 21:43 ` Alexander Gordeev
2014-03-06 21:50 ` Dan Williams
2014-03-07 7:49 ` [PATCH v2] " Alexander Gordeev
2014-04-21 13:36 ` Alexander Gordeev
2014-08-25 16:35 ` Alexander Gordeev
2014-08-25 16:31 ` Dan Williams
2014-03-06 20:11 ` [PATCH v2 RESEND 2/4] portdrv: " Alexander Gordeev
2014-03-13 3:56 ` Bjorn Helgaas [this message]
2014-04-14 16:18 ` Alexander Gordeev
2014-03-06 20:11 ` [PATCH v2 RESEND 3/4] tsi721: " Alexander Gordeev
2014-03-07 13:35 ` Bounine, Alexandre
2014-04-21 13:28 ` Alexander Gordeev
2014-03-06 20:11 ` [PATCH v2 RESEND 4/4] xhci: " Alexander Gordeev
2014-03-06 21:56 ` Sarah Sharp
2014-03-07 7:46 ` [PATCH v2 1/2] xhci: Cleanup xhci_setup_msi() and xhci_setup_msix() Alexander Gordeev
2014-03-07 7:48 ` [PATCH v2 2/2] xhci: Use pci_enable_msix_exact() instead of pci_enable_msix() Alexander Gordeev
2014-03-25 14:27 ` [PATCH v2 RESEND 4/4] " Alexander Gordeev
2014-04-02 11:41 ` Alexander Gordeev
2014-04-02 14:05 ` Mathias Nyman
2014-04-02 15:20 ` 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=20140313035634.GA26657@google.com \
--to=bhelgaas@google.com \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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.