From: Christoph Hellwig <hch@lst.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Alexander Gordeev <agordeev@redhat.com>, linux-pci@vger.kernel.org
Subject: convert the PCIe portdrv to pci_alloc_irq_vectors
Date: Wed, 1 Feb 2017 14:41:41 +0100 [thread overview]
Message-ID: <1485956503-8194-1-git-send-email-hch@lst.de> (raw)
Hi all,
this series has a small tweak to pci_alloc_irq_vectors and the conversion
of the PCIe portdrv to use pci_alloc_irq_vectors. Note that I could not
actually find a root port that uses MSI-X vectors - mine all either seem
to have no interrupts at all if they don't offer any interesting services
or a use a single MSI vector if hotplug capable, so the somewhat hairy
part of the patch isn't actually tested. If anyone has a chance to
test it (or carefully review it) that would be great.
next reply other threads:[~2017-02-01 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 13:41 Christoph Hellwig [this message]
2017-02-01 13:41 ` [PATCH 1/2] PCI/msi: check that we have a legacy interrupt line before using it Christoph Hellwig
2017-02-01 13:41 ` [PATCH 2/2] PCI/portdrv: use pci_irq_alloc_vectors Christoph Hellwig
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=1485956503-8194-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=agordeev@redhat.com \
--cc=bhelgaas@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).