From: Andrew Morton <akpm@linux-foundation.org>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Matt Porter <mporter@kernel.crashing.org>,
Alexandre Bounine <alexandre.bounine@idt.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] rapidio/tsi721: Use pci_enable_msix_exact() instead of pci_enable_msix()
Date: Tue, 13 May 2014 14:46:34 -0700 [thread overview]
Message-ID: <20140513144634.c7bc3d20db633f32fea913b6@linux-foundation.org> (raw)
In-Reply-To: <1399993292-31692-1-git-send-email-agordeev@redhat.com>
On Tue, 13 May 2014 17:01:32 +0200 Alexander Gordeev <agordeev@redhat.com> 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.
>
What (if any) runtime effect does this patch have?
> --- a/drivers/rapidio/devices/tsi721.c
> +++ b/drivers/rapidio/devices/tsi721.c
> @@ -768,15 +768,10 @@ static int tsi721_enable_msix(struct tsi721_device *priv)
> }
> #endif /* CONFIG_RAPIDIO_DMA_ENGINE */
>
> - err = pci_enable_msix(priv->pdev, entries, ARRAY_SIZE(entries));
> + err = pci_enable_msix_exact(priv->pdev, entries, ARRAY_SIZE(entries));
> if (err) {
> - if (err > 0)
> - dev_info(&priv->pdev->dev,
> - "Only %d MSI-X vectors available, "
> - "not using MSI-X\n", err);
> - else
> - dev_err(&priv->pdev->dev,
> - "Failed to enable MSI-X (err=%d)\n", err);
> + dev_err(&priv->pdev->dev,
> + "Failed to enable MSI-X (err=%d)\n", err);
> return err;
> }
>
> --
> 1.7.7.6
next prev parent reply other threads:[~2014-05-13 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 15:01 Alexander Gordeev
2014-05-13 15:20 ` Alexander Gordeev
2014-05-13 21:46 ` Andrew Morton [this message]
2014-05-14 4:54 ` Alexander Gordeev
2014-05-27 23:19 ` Bjorn Helgaas
2014-05-28 8:57 ` 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=20140513144634.c7bc3d20db633f32fea913b6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agordeev@redhat.com \
--cc=alexandre.bounine@idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mporter@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®