From: Dave Jiang <djiang@mvista•com>
To: Paul Mackerras <paulus@samba•org>
Cc: Doug Thompson <norsk5@yahoo•com>,
dfarnsworth@mvista•com, linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] powerpc: setup Marvell mv64x60 platform devices for EDAC
Date: Mon, 25 Jun 2007 09:09:35 -0700 [thread overview]
Message-ID: <467FE8BF.6060407@mvista.com> (raw)
In-Reply-To: <18047.24840.233508.259767@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Dave Jiang writes:
>
>> The mv64x60 EDAC driver can be found at:
>> http://bluesmoke.sourceforge.net/
>>
>> It's in development to be pushed into the kernel.
>
> Am I correct in thinking this patch is useless without that driver?
>
> Is that driver being submitted for 2.6.23? If so, who is submitting
> it and to whom? Does it look like it will be accepted?
>
> Paul.
Paul,
Yes you are correct. I have not yet submitted the driver to akpm. I'm waiting
for the core EDAC changes to be accepted, which are in the mm tree right now.
The driver relies on some new API changes to EDAC that are in the mm tree.
Without those changes the driver is pretty useless. The driver is publicly
available from the sourceforge EDAC SVN at the moment and patches against the
latest mm tree. If you like I can ask Doug Thompson (the EDAC maintainer) to
put the driver in the mm tree.
This is also the same for the mpc85xx EDAC driver. Of course that needs the
publish of the of_device patch.
--
------------------------------------------------------
Dave Jiang
Software Engineer
MontaVista Software, Inc.
http://www.mvista.com
------------------------------------------------------
prev parent reply other threads:[~2007-06-25 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 23:24 [PATCH] powerpc: setup Marvell mv64x60 platform devices for EDAC Dave Jiang
2007-05-23 20:23 ` Dale Farnsworth
2007-06-25 6:30 ` Paul Mackerras
2007-06-25 16:09 ` Dave Jiang [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=467FE8BF.6060407@mvista.com \
--to=djiang@mvista$(echo .)com \
--cc=dfarnsworth@mvista$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=norsk5@yahoo$(echo .)com \
--cc=paulus@samba$(echo .)org \
/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