From: Keith Busch <keith.busch@intel.com>
To: Oza Pawandeep <poza@codeaurora.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dongdong Liu <liudongdong3@huawei.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Wei Zhang <wzhang@fb.com>, Sinan Kaya <okaya@codeaurora.org>,
Timur Tabi <timur@codeaurora.org>
Subject: Re: [PATCH 0/4] Address error and recovery for AER and DPC
Date: Thu, 28 Dec 2017 10:34:29 -0700 [thread overview]
Message-ID: <20171228173428.GA16071@localhost.localdomain> (raw)
In-Reply-To: <1514370022-4431-1-git-send-email-poza@codeaurora.org>
On Wed, Dec 27, 2017 at 02:20:18AM -0800, Oza Pawandeep wrote:
> DPC should enumerate the devices after recovering the link, which is
> achieved by implementing error_resume callback.
Wouldn't that race with the link-up event that pciehp currently handles?
next prev parent reply other threads:[~2017-12-28 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 10:20 [PATCH 0/4] Address error and recovery for AER and DPC Oza Pawandeep
2017-12-27 10:20 ` [PATCH 1/4] PCI/AER: factor out error reporting from AER Oza Pawandeep
2017-12-28 15:36 ` kbuild test robot
2017-12-28 16:07 ` kbuild test robot
2017-12-27 10:20 ` [PATCH 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC Oza Pawandeep
2017-12-28 16:27 ` [RFC PATCH] PCI/DPC/AER: pci_find_dpc_dev() can be static kbuild test robot
2017-12-28 16:27 ` [PATCH 2/4] PCI/DPC/AER: Address Concurrency between AER and DPC kbuild test robot
2017-12-28 17:37 ` kbuild test robot
2017-12-28 18:07 ` kbuild test robot
2017-12-27 10:20 ` [PATCH 3/4] PCI/ERR: Do not do recovery if DPC service is active Oza Pawandeep
2017-12-27 10:20 ` [PATCH 4/4] PCI/DPC: Enumerate the devices after DPC trigger event Oza Pawandeep
2017-12-28 17:34 ` Keith Busch [this message]
2017-12-29 5:15 ` [PATCH 0/4] Address error and recovery for AER and DPC poza
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=20171228173428.GA16071@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=gabriele.paoloni@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=okaya@codeaurora.org \
--cc=pombredanne@nexb.com \
--cc=poza@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.org \
--cc=wzhang@fb.com \
/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).