From: "H. Peter Anvin" <hpa@zytor.com>
To: John Villalovos <john.l.villalovos@intel.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Yinghai Lu <yinghai@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
John Villalovos <jvillalo@redhat.com>,
prarit@redhat.com
Subject: Re: [PATCH 1/1 V2] x86, apic: Make "broken BIOS!!" messages unique
Date: Mon, 07 Feb 2011 13:25:55 -0800 [thread overview]
Message-ID: <4D506363.4030707@zytor.com> (raw)
In-Reply-To: <20110207135843.GA10121@linuxjohn3.jf.intel.com>
On 02/07/2011 05:58 AM, John Villalovos wrote:
>
> The 'inconceivable' messages are because it should not be possible to reach
> those code paths.
>
More standard terminology would be "invalid" or "impossible".
"Inconceivable" sounds like a combination of legal values which just
don't make sense.
-hpa
next prev parent reply other threads:[~2011-02-07 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 13:58 [PATCH 1/1 V2] x86, apic: Make "broken BIOS!!" messages unique John Villalovos
2011-02-07 21:25 ` H. Peter Anvin [this message]
2011-02-07 21:33 ` John Villalovos
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=4D506363.4030707@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=john.l.villalovos@intel.com \
--cc=jvillalo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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