Message-ID: <4D506525.8020605@redhat.com>
Date: Mon, 07 Feb 2011 16:33:25 -0500
From: John Villalovos <jvillalo@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc13 Thunderbird/3.1.7
MIME-Version: 1.0
To: "H. Peter Anvin" <hpa@zytor.com>
CC: John Villalovos <john.l.villalovos@intel.com>,
        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>, prarit@redhat.com
Subject: Re: [PATCH 1/1 V2] x86, apic: Make "broken BIOS!!" messages unique
References: <20110207135843.GA10121@linuxjohn3.jf.intel.com> <4D506363.4030707@zytor.com>
In-Reply-To: <4D506363.4030707@zytor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 735
Lines: 17

On 02/07/2011 04:25 PM, H. Peter Anvin wrote:
> 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.
To be honest I used it in homage to The Princess Bride movie.  And 
frankly it is 'inconcievable' that code will ever be called :)

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