From: Yijing Wang <wangyijing@huawei.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
Rafael <rjw@sisk.pl>, Hanjun Guo <guohanjun@huawei.com>,
<jiang.liu@huawei.com>, Oliver Neukum <oneukum@suse.de>,
Gu Zheng <guz.fnst@cn.fujitsu.com>
Subject: Re: [PATCH -v2 3/3] PCI,pciehp: use PCIe DSN to identify device change during suspend
Date: Fri, 12 Jul 2013 10:19:41 +0800 [thread overview]
Message-ID: <51DF67BD.6030706@huawei.com> (raw)
In-Reply-To: <1373553233.1349.15.camel@x61.thuisdomein>
On 2013/7/11 22:33, Paul Bolle wrote:
> On Thu, 2013-07-11 at 17:43 +0800, Yijing Wang wrote:
> [...]
>> diff --git a/drivers/pci/hotplug/pciehp_core.c b/drivers/pci/hotplug/pciehp_core.c
>> index 1542735..f2eb214 100644
>> --- a/drivers/pci/hotplug/pciehp_core.c
>> +++ b/drivers/pci/hotplug/pciehp_core.c
> [...]
>> @@ -315,6 +342,24 @@ static int pciehp_resume (struct pcie_device *dev)
>> if (status) {
>> if (list_empty(&pbus->devices))
>> pciehp_enable_slot(slot);
>> +
>> + if (device_serial_number_changed(pbus)) {
>> + /*
>> + * first power off slot, avoid the old driver
>> + * .remove() method touch the new hardware
>> + */
>> + if (POWER_CTRL(ctrl)) {
>> + retval = pciehp_power_off_slot(slot);
>> + if (retval) {
>> + ctrl_err(ctrl,
>> + "Issue of Slot Disable command failed\n");
>> + return 0;
>> + }
>> + msleep(1000);
>> + pciehp_unconfigure_device(slot);
>> + pciehp_enable_slot(slot);
>> + }
>> + }
>> } else if (!list_empty(&pbus->devices))
>> pciehp_disable_slot(slot);
>>
>
> It was surprisingly hard to see why the patch wouldn't apply to v3.10.
> It turns out the very last line of context is a line consisting of just
> a single tab. And in v3.10 it is an empty line.
>
> Is that lone tab perhaps an editing mistake on your side?
I will check this, thanks!
>
>
> Paul Bolle
>
>
> .
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2013-07-12 2:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:43 [PATCH -v2 0/3] Use PCIe DSN to improve pciehp_resume Yijing Wang
2013-07-11 9:43 ` [PATCH -v2 1/3] PCI: introduce PCIe Device Serial Number Capability support Yijing Wang
2013-07-11 9:51 ` Don Dutile
2013-07-11 20:09 ` Bjorn Helgaas
2013-07-11 18:18 ` Don Dutile
2013-07-12 2:39 ` Yijing Wang
2013-07-12 3:37 ` Bjorn Helgaas
2013-07-12 2:30 ` Yijing Wang
2013-07-12 1:38 ` Yijing Wang
2013-07-12 2:43 ` Don Dutile
2013-07-11 14:22 ` Paul Bolle
2013-07-12 1:55 ` Yijing Wang
2013-07-11 9:43 ` [PATCH -v2 2/3] PCI,pciehp: avoid add a device already exist before suspend during resume Yijing Wang
2013-07-11 14:27 ` Paul Bolle
2013-07-12 2:19 ` Yijing Wang
2013-07-11 9:43 ` [PATCH -v2 3/3] PCI,pciehp: use PCIe DSN to identify device change during suspend Yijing Wang
2013-07-11 10:04 ` Don Dutile
2013-07-11 14:33 ` Paul Bolle
2013-07-12 2:19 ` Yijing Wang [this message]
2013-07-11 14:19 ` [PATCH -v2 0/3] Use PCIe DSN to improve pciehp_resume Paul Bolle
2013-07-12 1:52 ` Yijing Wang
2013-07-13 10:20 ` Paul Bolle
2013-07-15 0:51 ` Yijing Wang
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=51DF67BD.6030706@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=pebolle@tiscali.nl \
--cc=rjw@sisk.pl \
/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).