From: Lukas Wunner <lukas@wunner.de>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, bhelgaas@google.com,
kbusch@kernel.org, mahesh@linux.ibm.com, oohall@gmail.com,
sathyanarayanan.kuppuswamy@linux.intel.com
Subject: Re: [PATCH v2 2/2] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd
Date: Fri, 15 Nov 2024 10:06:59 +0100 [thread overview]
Message-ID: <ZzcPMxWqtvDWh3cq@wunner.de> (raw)
In-Reply-To: <20241112135419.59491-3-xueshuai@linux.alibaba.com>
On Tue, Nov 12, 2024 at 09:54:19PM +0800, Shuai Xue wrote:
> The AER driver has historically avoided reading the configuration space of
> an endpoint or RCiEP that reported a fatal error, considering the link to
> that device unreliable.
It would be good if you could mention the relevant commit here:
9d938ea53b26 ("PCI/AER: Don't read upstream ports below fatal errors")
Thanks,
Lukas
next prev parent reply other threads:[~2024-11-15 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 13:54 [PATCH v2 0/2] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2024-11-12 13:54 ` [PATCH v2 1/2] PCI/DPC: Run recovery on device that detected the error Shuai Xue
2025-01-23 4:53 ` Sathyanarayanan Kuppuswamy
2025-01-23 7:03 ` Shuai Xue
2024-11-12 13:54 ` [PATCH v2 2/2] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2024-11-15 9:06 ` Lukas Wunner [this message]
2024-11-15 9:22 ` Shuai Xue
2024-11-15 20:20 ` Bowman, Terry
2024-11-16 12:44 ` Shuai Xue
2024-11-17 13:36 ` Shuai Xue
2024-11-25 5:43 ` Shuai Xue
2024-11-25 19:47 ` Bowman, Terry
2025-01-23 20:10 ` Sathyanarayanan Kuppuswamy
2025-01-24 1:45 ` Shuai Xue
2025-01-24 7:03 ` Sathyanarayanan Kuppuswamy
2024-12-24 11:03 ` [PATCH v2 0/2] " Shuai Xue
2025-01-22 10:59 ` Shuai Xue
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=ZzcPMxWqtvDWh3cq@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=xueshuai@linux.alibaba.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).