From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-pci@vger.kernel.org, mpe@ellerman.id.au,
bhelgaas@google.com, Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH 0/3] pci/hotplug/pnv-php: More bug fixes
Date: Thu, 16 Feb 2017 10:22:31 +1100 [thread overview]
Message-ID: <1487200954-14681-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
This series bases on the series: https://patchwork.ozlabs.org/patch/713513.
This series fixes couple of issues:
* Remove WARN_ON() in pnv_php_put_slot(). The parent slot's refcount
is decreased when releasing PCI slot. The parent slot can be NULL
and no need to give a warning.
* The MSI (or MSIx) could be enabled prior to load pnv-php.ko. A
backtrace is thrown when phv-php.ko attempts to enable MSI again.
PATCH[2/3] skips enabling surprise hotplug if MSI has been enabled
by other driver.
* PATCH[3/3] doesn't disable MSI that was enabled by other dirver.
Also, the upstream port of the PCI slot is disabled when it's
destroyed.
Gavin Shan (3):
pci/hotplug/pnv-php: Remove WARN_ON() in pnv_php_put_slot()
pci/hotplug/pnv-php: Disable surprise hotplug capability on conflicts
pci/hotplug/pnv-php: Disable MSI and PCI device properly
drivers/pci/hotplug/pnv_php.c | 32 +++++++++++++++++++++++---------
1 file changed, 23 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-15 23:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 23:22 Gavin Shan [this message]
2017-02-15 23:22 ` [PATCH 1/3] pci/hotplug/pnv-php: Remove WARN_ON() in pnv_php_put_slot() Gavin Shan
2017-02-16 4:46 ` Andrew Donnellan
2017-02-16 6:10 ` Vaibhav Jain
2017-02-19 11:33 ` [1/3] " Michael Ellerman
2017-02-15 23:22 ` [PATCH 2/3] pci/hotplug/pnv-php: Disable surprise hotplug capability on conflicts Gavin Shan
2017-02-16 4:31 ` Andrew Donnellan
2017-02-16 5:50 ` Gavin Shan
2017-02-16 6:11 ` Vaibhav Jain
2017-02-15 23:22 ` [PATCH 3/3] pci/hotplug/pnv-php: Disable MSI and PCI device properly Gavin Shan
2017-02-16 4:45 ` Andrew Donnellan
2017-02-16 14:09 ` [PATCH 0/3] pci/hotplug/pnv-php: More bug fixes Bjorn Helgaas
2017-02-16 22:38 ` Gavin Shan
2017-02-16 23:28 ` Bjorn Helgaas
2017-02-16 23:39 ` Gavin Shan
2017-02-17 11:13 ` Michael Ellerman
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=1487200954-14681-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).