From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: #v4.9+@gwshan.ozlabs.ibm.com, williel@supermicro.com.tw,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
stable@vger.kernel.org, hankmax0000@gmail.com
Subject: Re: [1/3] drivers/pci/hotplug: Handle presence detection change properly
Date: Thu, 16 Feb 2017 16:59:45 +1100 (AEDT) [thread overview]
Message-ID: <3vP58d6Dkhz9s8T@ozlabs.org> (raw)
In-Reply-To: <1484095808-24777-2-git-send-email-gwshan@linux.vnet.ibm.com>
On Wed, 2017-01-11 at 00:50:06 UTC, Gavin Shan wrote:
> The surprise hotplug is driven by interrupt in PowerNV PCI hotplug
> driver. In the interrupt handler, pnv_php_interrupt(), we bail when
> pnv_pci_get_presence_state() returns zero wrongly. It causes the
> presence change event is always ignored incorrectly.
>
> This fixes the issue by bailing on error (non-zero value) returned
> from pnv_pci_get_presence_state().
>
> Fixes: 360aebd85a4 ("drivers/pci/hotplug: Support surprise hotplug in powernv driver")
> Cc: stable@vger.kernel.org #v4.9+
> Reported-by: Hank Chang <hankmax0000@gmail.com>
> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> Tested-by: Willie Liauw <williel@supermicro.com.tw>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/d7d55536c6cd1f80295b6d7483ad05
cheers
next prev parent reply other threads:[~2017-02-16 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:50 [PATCH 0/3] powerpc/powernv: PCI hotplug fixes and improvement Gavin Shan
2017-01-11 0:50 ` [PATCH 1/3] drivers/pci/hotplug: Handle presence detection change properly Gavin Shan
2017-02-16 5:59 ` Michael Ellerman [this message]
2017-01-11 0:50 ` [PATCH 2/3] drivers/pci/hotplug: Fix initial state for empty slot Gavin Shan
2017-01-11 0:50 ` [PATCH 3/3] drivers/pci/hotplug: Mask PDC interrupt if required Gavin Shan
2017-01-31 5:42 ` [PATCH 0/3] powerpc/powernv: PCI hotplug fixes and improvement Gavin Shan
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=3vP58d6Dkhz9s8T@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=#v4.9+@gwshan.ozlabs.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=hankmax0000@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.org \
--cc=williel@supermicro.com.tw \
/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).