[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50DB8485.8010709@zytor.com>
Date: Wed, 26 Dec 2012 15:13:09 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: David Rientjes <rientjes@...gle.com>
CC: David Woodhouse <dwmw2@...radead.org>,
Ingo Molnar <mingo@...nel.org>, tglx@...utronix.de,
"H. Peter Anvin" <hpa@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/build] x86: Default to ARCH= x86 to avoid overriding
CONFIG_64BIT
On 12/26/2012 02:00 PM, David Rientjes wrote:
>
> In the past, "make randconfig" would always generate a
> kernel that _should_ boot on that machine unless there was an underlying
> bug that should be fixed.
>
Not even remotely true. There are tons of options which may not be set
that your machine needs, or you might set options that exclude support
for your CPU, for example.
Seriously, this is a bad joke.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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/
Powered by blists - more mailing lists