From: Oliver <oohall@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, Russell Currey <ruscur@russell.cc>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oliver OHalloran <oliveroh@au1.ibm.com>
Subject: Re: [PATCH] MAINTAINERS: Add PPC contacts for PCI core error handling
Date: Thu, 13 Sep 2018 21:07:12 +1000 [thread overview]
Message-ID: <CAOSf1CH39usAocrtuBnZaPdMBorO9GHrABrEgokxTo-pySUVEg@mail.gmail.com> (raw)
In-Reply-To: <d51126f75116534ec6ba6caee907b9db82363cc7.camel@kernel.crashing.org>
On Thu, Sep 13, 2018 at 6:35 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Wed, 2018-09-12 at 11:58 -0500, Bjorn Helgaas wrote:
>> > 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.
>
> Sounds good. Oliver, you want to be looped in as well ?
Sure, putting all of EEH on Sam is probably not a nice thing to do.
> Cheers,
> Ben.
>
>
next prev parent reply other threads:[~2018-09-13 11:07 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 [this message]
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=CAOSf1CH39usAocrtuBnZaPdMBorO9GHrABrEgokxTo-pySUVEg@mail.gmail.com \
--to=oohall@gmail.com \
--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=oliveroh@au1.ibm.com \
--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).