From: Doug Thompson <norsk5@yahoo•com>
To: Dave Jiang <djiang@mvista•com>, Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Andrew Kilkenny <akilkenny@xes-inc•com>,
Nate Case <ncase@xes-inc•com>
Subject: Re: [PATCH v2] edac: mpc85xx: Add support for MPC8572
Date: Tue, 7 Oct 2008 16:10:09 -0700 (PDT) [thread overview]
Message-ID: <5262.14504.qm@web50104.mail.re2.yahoo.com> (raw)
In-Reply-To: <48EB8AF1.6020600@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Dave Jiang <djiang@mvista•com> wrote: There's an SVN+quilt tree via sourceforge for EDAC. I have asked Doug to push
this patch upstream to the mm tree.
Kumar Gala wrote:
>
> On Sep 19, 2008, at 6:20 PM, Nate Case wrote:
>
>> From: Andrew Kilkenny
>>
>> This adds support for the dual-core MPC8572 processor. We have
>> to support making SPR changes on each core. Also, since we can
>> have multiple memory controllers sharing an interrupt, flag the
>> interrupts with IRQF_SHARED.
>>
>> Signed-off-by: Andrew Kilkenny
>> Signed-off-by: Nate Case
>> ---
>> drivers/edac/mpc85xx_edac.c | 28 +++++++++++++++++++++++-----
>> 1 files changed, 23 insertions(+), 5 deletions(-)
>
> Acked-by: Kumar Gala
>
> Guys, is there an edac git tree or something to create patches against?
> I've got one I've been sitting on but it should be updated based on
> Nate's patch.
>
> - k
the SVN repos is
svn checkout https://bluesmoke.svn.sourceforge.net/svnroot/bluesmoke/trunk
the info page is
http://bluesmoke.sourceforge.net/
doug t
W1DUG
[-- Attachment #2: Type: text/html, Size: 1663 bytes --]
next prev parent reply other threads:[~2008-10-07 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 23:20 [PATCH v2] edac: mpc85xx: Add support for MPC8572 Nate Case
2008-10-07 12:39 ` Kumar Gala
2008-10-07 16:14 ` Dave Jiang
2008-10-07 23:10 ` Doug Thompson [this message]
2008-10-08 6:01 ` Kumar Gala
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=5262.14504.qm@web50104.mail.re2.yahoo.com \
--to=norsk5@yahoo$(echo .)com \
--cc=akilkenny@xes-inc$(echo .)com \
--cc=djiang@mvista$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ncase@xes-inc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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