From: Michael Ellerman <mpe@ellerman.id.au>
To: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, Russell Currey <ruscur@russell.cc>,
linuxppc-dev@lists.ozlabs.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add PPC contacts for PCI core error handling
Date: Thu, 20 Sep 2018 09:46:07 +1000 [thread overview]
Message-ID: <878t3xaw5c.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180912165846.GH118330@bhelgaas-glaptop.roam.corp.google.com>
Bjorn Helgaas <helgaas@kernel.org> writes:
> On Wed, Sep 12, 2018 at 11:55:26AM -0500, Bjorn Helgaas wrote:
>> From: Bjorn Helgaas <bhelgaas@google.com>
>>
>> The original PCI error recovery functionality was for the powerpc-specific
>> IBM EEH feature. PCIe subsequently added some similar features, including
>> AER and DPC, that can be used on any architecture.
>>
>> We want the generic PCI core error handling support to work with all of
>> these features. Driver error recovery callbacks should be independent of
>> which feature the platform provides.
>>
>> Add the generic PCI core error recovery files to the powerpc EEH
>> MAINTAINERS entry so the powerpc folks will be copied on changes to the
>> generic PCI error handling strategy.
>
> I really want to make sure the powerpc folks are plugged into any PCI core
> error handling discussions. Please let me know if there's a better way
> than this patch, or if there are other people who should be added.
Yeah this is a good option.
We powerpc folks also need to do a better job of keeping an eye on PCI
patches, I've asked more of us to subscribe to linux-pci.
cheers
next prev parent reply other threads:[~2018-09-19 23:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 16:55 [PATCH] MAINTAINERS: Add PPC contacts for PCI core error handling Bjorn Helgaas
2018-09-12 16:58 ` Bjorn Helgaas
2018-09-13 2:26 ` Russell Currey
2018-09-14 0:05 ` Sam Bobroff
2018-09-13 8:35 ` Benjamin Herrenschmidt
2018-09-13 11:07 ` Oliver
2018-09-19 23:46 ` Michael Ellerman [this message]
2018-09-18 21:58 ` Bjorn Helgaas
2018-09-19 1:49 ` Russell Currey
2018-09-19 22:14 ` Bjorn Helgaas
2018-09-20 4:21 ` Sam Bobroff
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=878t3xaw5c.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=ruscur@russell.cc \
/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).