All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Borislav Petkov <borislav.petkov@amd.com>,
	linux-kernel@vger.kernel.org, Doug Thompson <norsk5@yahoo.com>
Subject: Re: [RFC PATCH 00/21] amd64_edac: EDAC module for AMD64
Date: Tue, 28 Apr 2009 12:58:13 -0700	[thread overview]
Message-ID: <20090428195813.GA4474@kroah.com> (raw)
In-Reply-To: <20090428113410.e0b04f94.akpm@linux-foundation.org>

On Tue, Apr 28, 2009 at 11:34:10AM -0700, Andrew Morton wrote:
> 
> (cc Doug.  He was omitted from the [0/n] email.  Please be careul about
> that)
> 
> On Tue, 28 Apr 2009 18:06:12 +0200
> Borislav Petkov <borislav.petkov@amd.com> wrote:
> 
> > On Tue, Apr 28, 2009 at 08:58:52AM -0700, Greg KH wrote:
> > > On Tue, Apr 28, 2009 at 05:05:52PM +0200, Borislav Petkov wrote:
> > > > Hi Andrew,
> > > > hi Greg,
> > > > 
> > > > I think you've already heard about this driver, so here is a first
> > > > upstream submission request. It is quite sizable but partly the reason
> > > > for it is that it handles ECC detection and reporting for all AMD
> > > > K8, F10h and F11h families. It also implements DRAM error injection
> > > > functionality, failing DIMM module detection and some other fun stuff
> > > > found on F10h and later CPUs.
> > > > 
> > > > We've been doing testing/bugfixing/scrubbing here for some time, have
> > > > converted it to using kernel facilities and basically removed some slack
> > > > from it like glue code due to it being maintained out-of-tree. Please
> > > > take a look and let us know of any objections/comments you might have so
> > > > that we could tackle them on time.
> > > 
> > > At first glance, it looks sane to me.
> > > 
> > > Want me to put it in my driver tree so it can show up in -next?  Or is
> > > there some other tree you want to use?
> > 
> > -next should be just fine, let the code see some more testing :).
> 
> I suspect we will need another iteration because of the rdmsr/wrmsr
> thing.
> 
> I normally merge EDAC patches via -mm but there will be little overlap
> with a new driver such as this and I still haven't got my junk into
> linux-next yet.  So whatever.

Ok, you can take them, I have enough patches in my tree :)

thanks,

greg k-h

      reply	other threads:[~2009-04-28 20:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 15:05 [RFC PATCH 00/21] amd64_edac: EDAC module for AMD64 Borislav Petkov
2009-04-28 15:05 ` [PATCH 01/21] amd64_edac: add PCI config register defines Borislav Petkov
2009-04-28 15:05 ` [PATCH 02/21] amd64_edac: add driver structs Borislav Petkov
2009-04-28 18:13   ` Andrew Morton
2009-04-28 19:02     ` Borislav Petkov
2009-04-28 15:05 ` [PATCH 03/21] amd64_edac: add memory scrubber interface Borislav Petkov
2009-04-28 15:05 ` [PATCH 04/21] amd64_edac: add sys addr to memory controller mapping helpers Borislav Petkov
2009-04-28 15:05 ` [PATCH 05/21] amd64_edac: add functionality to compute the DRAM hole Borislav Petkov
2009-04-28 15:05 ` [PATCH 06/21] amd64_edac: add DRAM address type conversion facilities Borislav Petkov
2009-04-28 15:05 ` [PATCH 07/21] amd64_edac: add helper to dump relevant registers Borislav Petkov
2009-04-28 15:06 ` [PATCH 08/21] amd64_edac: assign DRAM chip select base and mask in a family-specific way Borislav Petkov
2009-04-28 15:06 ` [PATCH 09/21] amd64_edac: add k8-specific methods Borislav Petkov
2009-04-28 15:06 ` [PATCH 10/21] amd64_edac: add f10-and-later methods-p1 Borislav Petkov
2009-04-28 15:06 ` [PATCH 11/21] amd64_edac: add f10-and-later methods-p2 Borislav Petkov
2009-04-28 15:06 ` [PATCH 12/21] amd64_edac: add f10-and-later methods-p3 Borislav Petkov
2009-04-28 15:06 ` [PATCH 13/21] amd64_edac: add per-family descriptors Borislav Petkov
2009-04-28 15:06 ` [PATCH 14/21] amd64_edac: add msr accessors operating on all cpus Borislav Petkov
2009-04-28 18:21   ` Andrew Morton
2009-04-28 18:31     ` H. Peter Anvin
2009-04-28 19:23     ` Borislav Petkov
2009-04-28 15:06 ` [PATCH 15/21] amd64_edac: add x4 chipkill syndrome mapping table Borislav Petkov
2009-04-28 15:06 ` [PATCH 16/21] amd64_edac: add error decoding logic Borislav Petkov
2009-04-28 15:06 ` [PATCH 17/21] amd64_edac: add EDAC core-related initializers Borislav Petkov
2009-04-28 15:06 ` [PATCH 18/21] amd64_edac: add ECC reporting initializers Borislav Petkov
2009-04-28 15:06 ` [PATCH 19/21] amd64_edac: add debugging/testing code Borislav Petkov
2009-04-28 18:30   ` Andrew Morton
2009-04-28 15:06 ` [PATCH 20/21] amd64_edac: add DRAM error injection logic using sysfs Borislav Petkov
2009-04-28 15:06 ` [PATCH 21/21] amd64_edac: add module registration routines Borislav Petkov
2009-04-28 15:58 ` [RFC PATCH 00/21] amd64_edac: EDAC module for AMD64 Greg KH
2009-04-28 16:06   ` Borislav Petkov
2009-04-28 18:34     ` Andrew Morton
2009-04-28 19:58       ` Greg KH [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=20090428195813.GA4474@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=borislav.petkov@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norsk5@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.