From: Borislav Petkov <bp@alien8.de>
To: "Chen, Gong" <gong.chen@linux.intel.com>
Cc: tony.luck@intel.com, naveen.n.rao@linux.vnet.ibm.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ACPI, APEI, GHES: Remove strict check for memory error handling
Date: Mon, 25 Nov 2013 18:13:49 +0100 [thread overview]
Message-ID: <20131125171349.GI6782@pd.tnic> (raw)
In-Reply-To: <1385363701-12387-1-git-send-email-gong.chen@linux.intel.com>
On Mon, Nov 25, 2013 at 02:15:00AM -0500, Chen, Gong wrote:
> Usually SCI is employed to handle corrected error, especially
> for memory corrected error but in fact SCI still can be used
> to handle any error like memory uncorrected error even fatal
> error if BIOS enable it. For this kind of situation, it
> should be logged, too.
>
> v2 -> v1: make the event record more precisely
>
> Signed-off-by: Chen, Gong <gong.chen@linux.intel.com>
Looks ok to me.
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-11-25 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 7:15 [PATCH v2 1/2] ACPI, APEI, GHES: Remove strict check for memory error handling Chen, Gong
2013-11-25 7:15 ` [PATCH v2 2/2] ACPI, APEI, GHES: Cleanup ghes codes " Chen, Gong
2013-11-26 6:54 ` Chen, Gong
2013-11-26 7:23 ` Borislav Petkov
2013-11-27 2:15 ` Chen, Gong
2013-12-14 13:42 ` Chen, Gong
2013-11-26 9:04 ` Naveen N. Rao
2013-12-21 12:41 ` Borislav Petkov
2013-11-25 17:13 ` Borislav Petkov [this message]
2013-11-26 9:02 ` [PATCH v2 1/2] ACPI, APEI, GHES: Remove strict check " Naveen N. Rao
2013-11-26 9:31 ` Chen, Gong
2013-12-14 13:42 ` Chen, Gong
2013-12-16 14:51 ` Borislav Petkov
2013-12-16 14:40 ` Chen, Gong
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=20131125171349.GI6782@pd.tnic \
--to=bp@alien8.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=tony.luck@intel.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.