From: Dave Jiang <djiang@mvista•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Andrew Kilkenny <akilkenny@xes-inc•com>,
Nate Case <ncase@xes-inc•com>, Doug Thompson <norsk5@yahoo•com>
Subject: Re: [PATCH v2] edac: mpc85xx: Add support for MPC8572
Date: Tue, 07 Oct 2008 09:14:41 -0700 [thread overview]
Message-ID: <48EB8AF1.6020600@mvista.com> (raw)
In-Reply-To: <9AE5B028-CEB5-456A-B97F-834D0A9B665A@kernel.crashing.org>
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 <akilkenny@xes-inc•com>
>>
>> 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 <akilkenny@xes-inc•com>
>> Signed-off-by: Nate Case <ncase@xes-inc•com>
>> ---
>> drivers/edac/mpc85xx_edac.c | 28 +++++++++++++++++++++++-----
>> 1 files changed, 23 insertions(+), 5 deletions(-)
>
> Acked-by: Kumar Gala <galak@kernel•crashing.org>
>
> 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
--
------------------------------------------------------
Dave Jiang
Software Engineer
MontaVista Software, Inc.
http://www.mvista.com
------------------------------------------------------
next prev parent reply other threads:[~2008-10-07 16:14 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 [this message]
2008-10-07 23:10 ` Doug Thompson
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=48EB8AF1.6020600@mvista.com \
--to=djiang@mvista$(echo .)com \
--cc=akilkenny@xes-inc$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ncase@xes-inc$(echo .)com \
--cc=norsk5@yahoo$(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