From: Len Brown <lenb@kernel.org>
To: Huang Ying <ying.huang@intel.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Tony Luck <tony.luck@intel.com>,
linux-acpi@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -v4 0/3] ACPI, APEI, Report GHES error information via printk
Date: Mon, 13 Dec 2010 23:43:47 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1012132343100.16730@x980> (raw)
In-Reply-To: <1291688551-14395-1-git-send-email-ying.huang@intel.com>
On Tue, 7 Dec 2010, Huang Ying wrote:
> The recent consensus is that hardware error should be reported via printk.
> This patch adds printk support to APEI GHES.
>
> v4:
>
> - Remove pr_pfx, use printk directly
v4 applied to acpi-test
thanks,
Len Brown, Intel Open Source Technology Center
>
> v3:
>
> - Add document for output format per Andrew's comments
> - Move pr_pfx into printk.h, hope it is useful for others too
> - Fixes some issues according to comments
>
> v2:
>
> - Some minor adjustment of PCIe error section definition and printk format
>
> [PATCH -v4 1/3] Add CPER PCIe error section structure and constants definition
> [PATCH -v4 2/3] ACPI, APEI, Add APEI generic error status printing support
> [PATCH -v4 3/3] ACPI, APEI, Report GHES error information via printk
>
prev parent reply other threads:[~2010-12-14 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 2:22 [PATCH -v4 0/3] ACPI, APEI, Report GHES error information via printk Huang Ying
2010-12-07 2:22 ` [PATCH -v4 1/3] Add CPER PCIe error section structure and constants definition Huang Ying
2010-12-07 2:22 ` [PATCH -v4 2/3] ACPI, APEI, Add APEI generic error status printing support Huang Ying
2010-12-07 2:22 ` [PATCH -v4 3/3] ACPI, APEI, Report GHES error information via printk Huang Ying
2010-12-14 4:43 ` Len Brown [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=alpine.LFD.2.00.1012132343100.16730@x980 \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox