linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Currey <ruscur@russell.cc>
To: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	sbobroff@linux.ibm.com
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linux-kernel@vger.kernel.org, oohall@gmail.com
Subject: Re: [PATCH] MAINTAINERS: Add PPC contacts for PCI core error handling
Date: Thu, 13 Sep 2018 12:26:55 +1000	[thread overview]
Message-ID: <94b8929d44af6dd965600b7d159458312d500582.camel@russell.cc> (raw)
In-Reply-To: <20180912165846.GH118330@bhelgaas-glaptop.roam.corp.google.com>

On Wed, 2018-09-12 at 11:58 -0500, Bjorn Helgaas wrote:
> 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.

I think this patch is definitely a good idea.

Alongside this (whether you want to include it in your patch or not, Bjorn),
Sam Bobroff should replace myself as maintainer.  He's been very active in fixing,
reworking and reviewing in EEH land and will probably do a better job of keeping
his finger on the pulse of the generic PCI error handling code than I did.

- Russell

> 
> > Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> > ---
> >  MAINTAINERS |    4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 7e10ba65bfe4..d6699597fd89 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -11202,6 +11202,10 @@ PCI ENHANCED ERROR HANDLING (EEH) FOR POWERPC
> >  M:	Russell Currey <ruscur@russell.cc>
> >  L:	linuxppc-dev@lists.ozlabs.org
> >  S:	Supported
> > +F:	Documentation/PCI/pci-error-recovery.txt
> > +F:	drivers/pci/pcie/aer.c
> > +F:	drivers/pci/pcie/dpc.c
> > +F:	drivers/pci/pcie/err.c
> >  F:	Documentation/powerpc/eeh-pci-error-recovery.txt
> >  F:	arch/powerpc/kernel/eeh*.c
> >  F:	arch/powerpc/platforms/*/eeh*.c
> > 

  reply	other threads:[~2018-09-13  2:27 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 [this message]
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
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=94b8929d44af6dd965600b7d159458312d500582.camel@russell.cc \
    --to=ruscur@russell.cc \
    --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=mpe@ellerman.id.au \
    --cc=oohall@gmail.com \
    --cc=paulus@samba.org \
    --cc=sbobroff@linux.ibm.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).