linux-kernel - Re: [PATCH -v4 0/3] ACPI, APEI, Report GHES error information via printk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.00.1012132343100.16730@x980>
Date:	Mon, 13 Dec 2010 23:43:47 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Huang Ying <ying.huang@...el.com>
Cc:	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>,
	Tony Luck <tony.luck@...el.com>, linux-acpi@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH -v4 0/3] ACPI, APEI,
 Report GHES error information via printk

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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/