From: Borislav Petkov <borislav.petkov@amd.com>
To: Martin Cracauer <cracauer@cons.org>
Cc: bluesmoke-devel@lists.sourceforge.net
Subject: Re: amd64_edac driver availability, status?
Date: Mon, 12 Oct 2009 07:45:09 +0200 [thread overview]
Message-ID: <20091012054509.GC27799@aftab> (raw)
In-Reply-To: <20091009211423.GA35447@cons.org>
On Fri, Oct 09, 2009 at 05:14:23PM -0400, Martin Cracauer wrote:
> Hello,
>
> I can't seem to find md64_edac, neither in the mainline kernel, nor
> the tarball nor in
it is in mainline since 2.6.31:
[boris $] ls -l drivers/edac/amd64_edac*
-rw-r--r-- 1 boris boris 93473 2009-10-08 08:18 drivers/edac/amd64_edac.c
-rw-r--r-- 1 boris boris 5406 2009-10-08 08:18 drivers/edac/amd64_edac_dbg.c
-rw-r--r-- 1 boris boris 17286 2009-10-08 08:18 drivers/edac/amd64_edac.h
-rw-r--r-- 1 boris boris 4304 2009-08-26 07:51 drivers/edac/amd64_edac_inj.c
--
Regards/Gruss,
Boris.
Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
next prev parent reply other threads:[~2009-10-12 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:14 amd64_edac driver availability, status? Martin Cracauer
2009-10-12 5:45 ` Borislav Petkov [this message]
2009-10-12 21:42 ` Doug Thompson
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=20091012054509.GC27799@aftab \
--to=borislav.petkov@amd.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=cracauer@cons.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 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.