From: Doug Thompson <norsk5@yahoo.com>
To: dougthompson@xmission.com, Peter Tyser <ptyser@xes-inc.com>
Cc: kolifer@gmail.com, akpm@linux-foundation.org,
bluesmoke-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] edac: mpc85xx fsb ecc
Date: Thu, 4 Feb 2010 21:48:34 -0800 (PST) [thread overview]
Message-ID: <324607.19392.qm@web50108.mail.re2.yahoo.com> (raw)
In-Reply-To: <1265304134.14589.152.camel@localhost.localdomain>
--- On Thu, 2/4/10, Peter Tyser <ptyser@xes-inc.com> wrote:
> From: Peter Tyser <ptyser@xes-inc.com>
> Subject: Re: [PATCH 6/7] edac: mpc85xx fsb ecc
> To: dougthompson@xmission.com
> Cc: kolifer@gmail.com, akpm@linux-foundation.org, bluesmoke-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
> Date: Thursday, February 4, 2010, 10:22 AM
> Hi Doug and Konstantin,
>
> On Wed, 2010-02-03 at 23:46 -0700, dougthompson@xmission.com
> wrote:
> > From: Konstantin Olifer <kolifer@gmail.com>
> >
> > Patch is for Kernel 2.6.33. e752x_edac suppose that
> fsb ECC exist, for example, on
> > Celeron + 3100. That is wrong.
> > ECC FSB supported only on Xeon for our vision
> (www.setdsp.ru) and datasheet from developer intel www.
> > Fixed.
> > Signed-off-by: Konstantin Olifer <kolifer@gmail.com>
> > Signed-off-by: Doug Thompson <dougthompson@xmission.com>
> > ---
> > e752x_edac.c | 10 ++--------
> > 1 file changed, 2 insertions(+), 8 deletions(-)
>
> It looks like 6/7 and 7/7 in this series have the wrong
> subject/title.
> Patches 6 and 7 are for the e752x instead of the mpc85xx.
my bad while I was constructing the titles. missed the driver name
thanks andrew for fixing that
doug t
prev parent reply other threads:[~2010-02-05 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 6:46 dougthompson
2010-02-04 17:22 ` Peter Tyser
2010-02-05 5:48 ` Doug Thompson [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=324607.19392.qm@web50108.mail.re2.yahoo.com \
--to=norsk5@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dougthompson@xmission.com \
--cc=kolifer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptyser@xes-inc.com \
/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
all inboxes | Powered by JetHome®