From: Lukas Wunner <lukas@wunner.de>
To: Sinan Kaya <okaya@kernel.org>
Cc: poza@codeaurora.org, linux-pci@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Keith Busch <keith.busch@intel.com>,
linux-pci-owner@vger.kernel.org
Subject: Re: [PATCH v7 1/1] PCI: pciehp: Ignore link events when there is a fatal error pending
Date: Mon, 6 Aug 2018 18:44:45 +0200 [thread overview]
Message-ID: <20180806164445.GA28786@wunner.de> (raw)
In-Reply-To: <22ce7172-b028-c0b1-d117-8096e016b15b@kernel.org>
On Mon, Aug 06, 2018 at 11:06:48AM -0400, Sinan Kaya wrote:
> Surprise Link Down is also a fatal error.
Seriously? On a Downstream Port which has the Hot-Plug Surprise bit
in the Slot Capabilities register set, Surprise Link Down is a fatal
error? That would seem somewhat contradictory. Do you have a
section number in the PCIe Base Spec for this?
Thanks,
Lukas
next prev parent reply other threads:[~2018-08-06 18:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 22:51 [PATCH v7 0/1] PCI: Handle conflict between hotplug and error handling Sinan Kaya
2018-08-05 22:51 ` [PATCH v7 1/1] PCI: pciehp: Ignore link events when there is a fatal error pending Sinan Kaya
2018-08-06 7:51 ` poza
2018-08-06 9:26 ` Lukas Wunner
2018-08-06 14:55 ` poza
2018-08-06 15:04 ` Sinan Kaya
2018-08-06 15:06 ` Sinan Kaya
2018-08-06 15:12 ` poza
2018-08-06 16:34 ` Sinan Kaya
2018-08-06 16:44 ` Lukas Wunner [this message]
2018-08-06 16:49 ` Sinan Kaya
2018-08-06 17:03 ` Sinan Kaya
2018-08-06 17:05 ` Lukas Wunner
2018-08-06 17:09 ` Sinan Kaya
2018-08-06 9:30 ` Lukas Wunner
2018-09-04 18:18 ` [PATCH v7 0/1] PCI: Handle conflict between hotplug and error handling Bjorn Helgaas
2018-09-04 18:28 ` Sinan Kaya
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=20180806164445.GA28786@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=okaya@kernel.org \
--cc=poza@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.