From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <chris.friesen@genband.com>
Cc: b25806@freescale.com, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: curious why mpc85xx/edac/pcie patch series was never picked up
Date: Wed, 23 Nov 2011 09:14:27 +1100 [thread overview]
Message-ID: <1322000067.14573.12.camel@pasglop> (raw)
In-Reply-To: <4ECBDE98.8090705@genband.com>
On Tue, 2011-11-22 at 11:40 -0600, Chris Friesen wrote:
> We're doing some work with an mpc85xx-based board and someone pointed to
> a patch adding PCI/PCIE error interrupt edac support that was proposed
> by Lan Chunhe over a year ago:
>
> http://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/086930.html
>
> For some reason this doesn't appear to have been picked up for mainline,
> and I'm curious why not--is there something wrong with it?
Kumar ? What's up there ? Is that a miscommunication with the edac folks
or we just lost it between the cracks ?
Cheers,
Ben.
prev parent reply other threads:[~2011-11-22 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 17:40 curious why mpc85xx/edac/pcie patch series was never picked up Chris Friesen
2011-11-22 22:14 ` Benjamin Herrenschmidt [this message]
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=1322000067.14573.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=b25806@freescale.com \
--cc=chris.friesen@genband.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.