mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Russell Currey <ruscur@russell.cc>
Cc: linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	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,
	sbobroff@linux.ibm.com
Subject: Re: [PATCH] MAINTAINERS: Add PPC contacts for PCI core error handling
Date: Wed, 19 Sep 2018 17:14:52 -0500	[thread overview]
Message-ID: <20180919221452.GC261184@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <1020abbb3d8a8f121d25da7327e296cfa1aaa698.camel@russell.cc>

On Wed, Sep 19, 2018 at 11:49:26AM +1000, Russell Currey wrote:
> On Tue, 2018-09-18 at 16: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.
> > > 
> > > Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> > 
> > I applied the following to for-linus for v4.19.  Russell, if you want
> > to be removed, let me know and I'll do that.
> 
> Oliver's email address for kernel stuff is oohall@gmail.com, I think benh has been
> CCing his IBM address.  But other than that,
> 
> Acked-by: Russell Currey <ruscur@russell.cc>

I updated Oliver's email address and added your ack, thanks!

  reply	other threads:[~2018-09-19 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 16:55 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
2018-09-18 21:58 ` Bjorn Helgaas
2018-09-19  1:49   ` Russell Currey
2018-09-19 22:14     ` Bjorn Helgaas [this message]
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=20180919221452.GC261184@bhelgaas-glaptop.roam.corp.google.com \
    --to=helgaas@kernel.org \
    --cc=benh@kernel.crashing.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=ruscur@russell.cc \
    --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

all inboxes | Powered by JetHome®