From: Bjorn Helgaas <helgaas@kernel.org>
To: xuyandong <xuyandong2@huawei.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Ofer Hayut <ofer@lightbitslabs.com>,
Roy Shterman <roys@lightbitslabs.com>,
Keith Busch <keith.busch@intel.com>,
"Wangzhou (B)" <wangzhou1@hisilicon.com>
Subject: Re: [PATCH v3] PCI: avoid bridge feature re-probing on hotplug
Date: Tue, 22 Jan 2019 12:58:38 -0600 [thread overview]
Message-ID: <20190122185838.GB14636@google.com> (raw)
In-Reply-To: <7CECC2DFC21538489F72729DF5EFB4D909EC77D4@dggemm501-mbs.china.huawei.com>
On Tue, Jan 22, 2019 at 05:31:10AM +0000, xuyandong wrote:
> Hi Bjorn and Michael
>
> After trying to reproduce the problem for a whole day, the bug did not show up
> any more. So I think the new patch does solve this problem.
Thank you very much for testing this!
I'd like to give you the appropriate credit in the changelog, but I don't
know exactly how your name should be spelled and capitalized. Is the
following what you want? If not, let me know and I'll correct it.
Reported-by: xuyandong <xuyandong2@huawei.com>
Tested-by: xuyandong <xuyandong2@huawei.com>
Bjorn
prev parent reply other threads:[~2019-01-22 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 0:45 [PATCH v2] PCI: avoid bridge feature re-probing on hotplug Michael S. Tsirkin
2018-12-20 19:49 ` Bjorn Helgaas
2018-12-20 21:26 ` Michael S. Tsirkin
2018-12-20 22:31 ` Bjorn Helgaas
2018-12-20 22:36 ` Michael S. Tsirkin
2019-01-07 15:01 ` Michael S. Tsirkin
2019-01-15 4:07 ` Michael S. Tsirkin
2019-01-15 22:23 ` Bjorn Helgaas
2019-01-19 20:12 ` [PATCH v3] " Bjorn Helgaas
2019-01-20 14:49 ` Michael S. Tsirkin
2019-01-22 5:31 ` xuyandong
2019-01-22 13:53 ` Michael S. Tsirkin
2019-01-22 18:58 ` Bjorn Helgaas [this message]
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=20190122185838.GB14636@google.com \
--to=helgaas@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ofer@lightbitslabs.com \
--cc=roys@lightbitslabs.com \
--cc=sagi@grimberg.me \
--cc=wangzhou1@hisilicon.com \
--cc=xuyandong2@huawei.com \
--cc=yinghai@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).