From: Borislav Petkov <bp@alien8.de>
To: Jacob Shin <jacob.shin@amd.com>
Cc: Doug Thompson <dougthompson@xmission.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/2] MCE, AMD: MCE decoding support for AMD Family 16h
Date: Thu, 20 Dec 2012 20:17:24 +0100 [thread overview]
Message-ID: <20121220191724.GF26635@liondog.tnic> (raw)
In-Reply-To: <1355864771-13839-1-git-send-email-jacob.shin@amd.com>
On Tue, Dec 18, 2012 at 03:06:09PM -0600, Jacob Shin wrote:
> The following patchset enables MCE decoding support for AMD Family 16h
> processors.
>
> Changes in V2:
> * Changed if/else style and pr_cont usage per feedback from:
> https://lkml.org/lkml/2012/12/17/365
>
> * Merged f14h and f16h mc0 and mc2 decoding into common function per
> feedback from: https://lkml.org/lkml/2012/12/18/269
>
> * Fixed typo in INT_ERROR decoding.
>
> Jacob Shin (2):
> MCE, AMD: Make MC2 decoding part of amd_decoder_ops as well
> MCE, AMD: MCE decoding support for AMD Family 16h
Ok, applied and pushed out to:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git edac-for-3.9
Please take a look and give them a run.
Also, I have a python injection script with which you could test
your decoding code on F16h - no real MCEs are getting injected, but
software-only. Let me know if you want it and I'll dust it off and send
it to you along with instructions on how to use it.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2012-12-20 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 21:06 Jacob Shin
2012-12-18 21:06 ` [PATCH 1/2] MCE, AMD: Make MC2 decoding part of amd_decoder_ops as well Jacob Shin
2012-12-18 21:06 ` [PATCH 2/2] MCE, AMD: MCE decoding support for AMD Family 16h Jacob Shin
2012-12-18 22:10 ` Joe Perches
2012-12-18 22:56 ` Borislav Petkov
2012-12-20 19:20 ` Borislav Petkov
2012-12-20 19:17 ` Borislav Petkov [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=20121220191724.GF26635@liondog.tnic \
--to=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=jacob.shin@amd.com \
--cc=linux-edac@vger.kernel.org \
--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®