linux-kernel - Re: [PATCH 1/4] edac: mpc85xx add P2020DS support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <567174.85150.qm@web50109.mail.re2.yahoo.com>
Date:	Wed, 15 Jul 2009 16:12:54 -0700 (PDT)
From:	Doug Thompson <norsk5@...oo.com>
To:	dougthompson@...ssion.com,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	bluesmoke-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] edac: mpc85xx add P2020DS support



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

> From: Andrew Morton <akpm@...ux-foundation.org>
> Subject: Re: [PATCH 1/4] edac: mpc85xx add P2020DS support
> To: dougthompson@...ssion.com
> Cc: bluesmoke-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
> Date: Wednesday, July 15, 2009, 1:40 PM
> On Wed, 15 Jul 2009 11:38:49 -0600
> dougthompson@...ssion.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@...driver.com>
> > Acked-by: Dave Jiang <djiang@...sta.com>
> > Signed-off-by: Doug Thompson <dougthompson@...ssion.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/