From: Bjorn Helgaas <helgaas@kernel.org>
To: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>
Cc: "Carlis, Matthew" <mattc@purestorage.com>,
"Smita.KoralahalliChannabasappa@amd.com"
<Smita.KoralahalliChannabasappa@amd.com>,
"Preble, Adam C" <adam.c.preble@intel.com>,
"Schofield, Alison" <alison.schofield@intel.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"bp@alien8.de" <bp@alien8.de>,
"Peng, Chao P" <chao.p.peng@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"erwin.tsaur@intel.com" <erwin.tsaur@intel.com>,
"Wanyan, Feiting" <feiting.wanyan@intel.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"lukas@wunner.de" <lukas@wunner.de>,
"mahesh@linux.ibm.com" <mahesh@linux.ibm.com>,
"oohall@gmail.com" <oohall@gmail.com>,
"qingshun.wang@linux.intel.com" <qingshun.wang@linux.intel.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"rrichter@amd.com" <rrichter@amd.com>,
"Kuppuswamy,
Sathyanarayanan" <sathyanarayanan.kuppuswamy@intel.com>,
"Luck, Tony" <tony.luck@intel.com>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"Wang, Yudong" <yudong.wang@intel.com>,
"Saggi, Meeta" <msaggi@purestorage.com>,
"sconnor@purestorage.com" <sconnor@purestorage.com>,
"Karkare, Ashish" <ashishk@purestorage.com>,
"rhan@purestorage.com" <rhan@purestorage.com>,
"Rangi, Jasjeet" <jrangi@purestorage.com>,
"Govindjee, Arjun" <agovindjee@purestorage.com>,
"Amstadt, Bob" <bamstadt@purestorage.com>
Subject: Re: [PATCH v5 0/2] PCI/AER: Handle Advisory Non-Fatal error
Date: Fri, 22 Aug 2025 11:51:12 -0500 [thread overview]
Message-ID: <20250822165112.GA688464@bhelgaas> (raw)
In-Reply-To: <IA3PR11MB9136FCB8C778B0AE08BF8DB5923DA@IA3PR11MB9136.namprd11.prod.outlook.com>
On Fri, Aug 22, 2025 at 01:45:30AM +0000, Duan, Zhenzhong wrote:
> Hi Matthew,
>
> Feel free to take it over if you are interested. Maintainer didn't
> respond to this series, perhaps he expects some improvement in the
> series.
I'm terribly sorry, this is my fault. It just fell off my list for no
good reason. Matthew, if you are able to test and/or provide a
Reviewed-by, that would be the best thing you can do to move this
forward (although neither is actually necessary).
Bjorn
> >-----Original Message-----
> >From: Matthew W Carlis <mattc@purestorage.com>
> >Subject: [PATCH v5 0/2] PCI/AER: Handle Advisory Non-Fatal error
> >
> >Hello. My team had independently started to make a change similar to this
> >before realizing that someone had already taken a stab at it. It is highly
> >desirable in my mind to have an improved handling of Advisory Errors in
> >the upstream kernel. Is there anything we can do to help move this effort
> >along? Perhaps testing? We have a decent variety of system configurations &
> >are able to inject various kinds of errors via special devices/commands etc.
> >
> >Thanks,
> >-Matt
next prev parent reply other threads:[~2025-08-22 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 2:58 [PATCH v5 0/2] PCI/AER: Handle Advisory Non-Fatal error Zhenzhong Duan
2024-06-20 2:58 ` [PATCH v5 1/2] PCI/AER: Clear UNCOR_STATUS bits that might be ANFE Zhenzhong Duan
2025-08-22 17:20 ` Bjorn Helgaas
2024-06-20 2:58 ` [PATCH v5 2/2] PCI/AER: Print " Zhenzhong Duan
2025-08-22 17:27 ` Bjorn Helgaas
2025-08-29 21:18 ` Bjorn Helgaas
2024-07-12 9:56 ` [PATCH v5 0/2] PCI/AER: Handle Advisory Non-Fatal error Duan, Zhenzhong
2025-08-21 16:58 ` Matthew W Carlis
2025-08-22 1:45 ` Duan, Zhenzhong
2025-08-22 16:51 ` Bjorn Helgaas [this message]
2025-08-22 18:15 ` Matthew W Carlis
2025-08-27 9:42 ` Duan, Zhenzhong
2025-08-28 1:00 ` Matthew W Carlis
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=20250822165112.GA688464@bhelgaas \
--to=helgaas@kernel.org \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=adam.c.preble@intel.com \
--cc=agovindjee@purestorage.com \
--cc=alison.schofield@intel.com \
--cc=ashishk@purestorage.com \
--cc=bamstadt@purestorage.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=chao.p.peng@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=erwin.tsaur@intel.com \
--cc=feiting.wanyan@intel.com \
--cc=ira.weiny@intel.com \
--cc=james.morse@arm.com \
--cc=jrangi@purestorage.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=mattc@purestorage.com \
--cc=msaggi@purestorage.com \
--cc=oohall@gmail.com \
--cc=qingshun.wang@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rhan@purestorage.com \
--cc=rrichter@amd.com \
--cc=sathyanarayanan.kuppuswamy@intel.com \
--cc=sconnor@purestorage.com \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
--cc=yudong.wang@intel.com \
--cc=zhenzhong.duan@intel.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).