From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: [PATCH 0/2] Generic hardware error reporting support Date: Wed, 24 Nov 2010 23:19:08 -0500 (EST) Message-ID: References: <1290154233-28695-1-git-send-email-ying.huang@intel.com> <4CE7CF95.2040608@teksavvy.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from vms173017pub.verizon.net ([206.46.173.17]:56951 "EHLO vms173017pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247Ab0KYETq (ORCPT ); Wed, 24 Nov 2010 23:19:46 -0500 In-reply-to: <4CE7CF95.2040608@teksavvy.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Mark Lord Cc: huang ying , Linus Torvalds , Huang Ying , linux-kernel@vger.kernel.org, Andi Kleen , linux-acpi@vger.kernel.org, Peter Zijlstra , Andrew Morton , Ingo Molnar , Mauro Carvalho Chehab , Borislav Petkov , Thomas Gleixner > If you (and the code) are absolutely certain that a particular error instance > is totally due to the BIOS, then stick the words "BIOS ERROR" into the > printk(). FYI, trenn added some printk prefixes for this case a while back; #define FW_BUG "[Firmware Bug]: " #define FW_WARN "[Firmware Warn]: " #define FW_INFO "[Firmware Info]: " cheers, -Len Brown, Intel Open Source Technology Center