From: Len Brown <lenb@kernel.org>
To: Mark Lord <kernel@teksavvy.com>
Cc: huang ying <huang.ying.caritas@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
linux-acpi@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] Generic hardware error reporting support
Date: Wed, 24 Nov 2010 23:19:08 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1011242316390.637@x980> (raw)
In-Reply-To: <4CE7CF95.2040608@teksavvy.com>
> 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
next prev parent reply other threads:[~2010-11-25 4:19 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 8:10 [PATCH 0/2] Generic hardware error reporting support Huang Ying
2010-11-19 8:10 ` [PATCH 1/2] Generic hardware error reporting mechanism Huang Ying
2010-11-19 8:45 ` Huang Ying
2010-11-19 13:56 ` boris
2010-11-19 13:56 ` boris
2010-11-20 2:52 ` huang ying
2010-11-20 2:52 ` huang ying
2010-11-20 9:00 ` Borislav Petkov
2010-11-20 9:00 ` Borislav Petkov
2010-11-20 11:51 ` huang ying
2010-11-20 11:51 ` huang ying
2010-11-19 8:10 ` [PATCH 2/2] Hardware error record persistent support Huang Ying
2010-11-19 15:52 ` Linus Torvalds
2010-11-19 15:52 ` Linus Torvalds
2010-11-19 20:01 ` Andrew Morton
2010-11-20 1:09 ` huang ying
2010-11-20 1:09 ` huang ying
2010-11-19 8:13 ` [PATCH 0/2] Generic hardware error reporting support Huang Ying
2010-11-19 11:22 ` Peter Zijlstra
2010-11-19 11:54 ` huang ying
2010-11-19 12:02 ` Peter Zijlstra
2010-11-19 12:48 ` huang ying
2010-11-19 12:48 ` huang ying
2010-11-19 12:55 ` Peter Zijlstra
2010-11-19 13:06 ` huang ying
2010-11-19 13:18 ` Peter Zijlstra
2010-11-19 13:28 ` huang ying
2010-11-19 13:37 ` Peter Zijlstra
2010-11-19 13:49 ` huang ying
2010-11-19 15:56 ` Linus Torvalds
2010-11-20 2:04 ` huang ying
2010-11-20 2:04 ` huang ying
2010-11-20 2:15 ` Linus Torvalds
2010-11-20 7:11 ` huang ying
2010-11-20 13:39 ` Mark Lord
2010-11-20 23:44 ` huang ying
2010-11-25 4:19 ` Len Brown [this message]
[not found] ` <AANLkTinAZgHbexU+LTUZHs-+7C0N990=kyuO-USV1Ncp@mail.gmail.com>
2010-11-20 23:57 ` Linus Torvalds
2010-11-20 23:57 ` Linus Torvalds
2010-11-21 0:42 ` huang ying
2010-11-21 0:50 ` Linus Torvalds
2010-11-21 1:06 ` huang ying
2010-11-21 1:06 ` huang ying
2010-11-22 23:43 ` Mark Lord
2010-11-23 0:29 ` Huang Ying
2010-11-25 2:41 ` Mark Lord
2010-11-25 4:27 ` Len Brown
2010-11-30 15:09 ` Mauro Carvalho Chehab
2010-11-25 4:35 ` Huang Ying
2010-11-21 0:50 ` Elias Gabriel Amaral da Silva
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.1011242316390.637@x980 \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=huang.ying.caritas@gmail.com \
--cc=kernel@teksavvy.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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 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.