mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug Thompson <norsk5@yahoo.com>
To: dougthompson@xmission.com, Andrew Morton <akpm@linux-foundation.org>
Cc: bluesmoke-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] edac: mpc85xx add P2020DS support
Date: Wed, 15 Jul 2009 16:12:54 -0700 (PDT)	[thread overview]
Message-ID: <567174.85150.qm@web50109.mail.re2.yahoo.com> (raw)
In-Reply-To: <20090715124011.276d2c88.akpm@linux-foundation.org>



--- On Wed, 7/15/09, Andrew Morton <akpm@linux-foundation.org> wrote:

> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: Re: [PATCH 1/4] edac: mpc85xx add P2020DS support
> To: dougthompson@xmission.com
> Cc: bluesmoke-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
> Date: Wednesday, July 15, 2009, 1:40 PM
> On Wed, 15 Jul 2009 11:38:49 -0600
> dougthompson@xmission.com
> wrote:
> 
> > Based on Kumar's new compatible types patch, add P2020
> into
> > MPC85xx EDAC compatible lists so that EDAC can
> recognize
> > P2020 meomry controller and L2 cache controller and
> export
> > the relevant fields to sysfs.
> > 
> > EDAC MPC85xx DDR3 support is needed if DDR3 memory
> stick is
> > installed on a P2020DS board so that EDAC core can
> recognize
> > DDR3 memory type.
> > 
> > Signed-off-by: Yang Shi <yang.shi@windriver.com>
> > Acked-by: Dave Jiang <djiang@mvista.com>
> > Signed-off-by: Doug Thompson <dougthompson@xmission.com>
> 
> The way the first two patches were sent indicates that you
> were their
> primary author.  Was that intended?


mmm, darn I missed that. No I am NOT the author. The first signed-off-by lines are the respective authors.

Not intended

> 
> Do you think that any/all of these should be in
> 2.6.31?  2.6.30.x?  If
> so, why?

The x38 fix could probably go into 2.6.31 as that addressing of the register does seem off with an ODD address and might/should cause bad data corruption at best, a fault at worst, IMHO. Maybe 2.6.30 as well

The resource fix patch probably does NOT need to go in, as the code looks to work now as is. It is just cleanup fix.

The mpc83xx patch was okay'd for queue into 2.6.32 only.

the mv64x patch is probably also for 2.6.32 since it is new addition

> 
> Thanks.
> 

thx

doug t

      reply	other threads:[~2009-07-15 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 17:38 dougthompson
2009-07-15 19:40 ` Andrew Morton
2009-07-15 23:12   ` 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=567174.85150.qm@web50109.mail.re2.yahoo.com \
    --to=norsk5@yahoo.com \
    --cc=akpm@linux-foundation.org \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=dougthompson@xmission.com \
    --cc=linux-kernel@vger.kernel.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 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®