[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aG_0K7Zx5WpQHGJE@smile.fi.intel.com>
Date: Thu, 10 Jul 2025 20:11:07 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH v2 1/1] x86/defconfigs: Explicitly unset CONFIG_64BIT in
i386_defconfig
On Thu, Jun 26, 2025 at 06:00:34PM +0300, Andy Shevchenko wrote:
> A recent refresh of the defconfigs got rid of the following
> (unset) configuration option:
>
> # CONFIG_64BIT is not set
>
> Innocuous as it seems, when the configuration file is saved again
> the behavior is changed so that CONFIG_64BIT=y.
>
> Currently,
>
> $ make i386_defconfig
> $ grep CONFIG_64BIT .config
> CONFIG_64BIT=y
>
> whereas previously (and with this patch):
>
> $ make i386_defconfig
> $ grep CONFIG_64BIT .config
> # CONFIG_64BIT is not set
>
> This was found by cross-compilation of the 32-bit kernel on 64-bit machine
> with the result of non-bootable kernel on Intel Galileo Gen 2 board.
>
> Restore the missing explicitly unset CONFIG_64BIT in 32-bit defconfig.
Can it be applied now?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists