From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>, linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2 1/1] x86/defconfigs: Explicitly unset CONFIG_64BIT in i386_defconfig
Date: Thu, 10 Jul 2025 20:11:07 +0300 [thread overview]
Message-ID: <aG_0K7Zx5WpQHGJE@smile.fi.intel.com> (raw)
In-Reply-To: <20250626150118.318836-1-andriy.shevchenko@linux.intel.com>
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
next prev parent reply other threads:[~2025-07-10 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 15:00 Andy Shevchenko
2025-07-10 17:11 ` Andy Shevchenko [this message]
2025-07-14 14:29 ` Borislav Petkov
2025-07-14 15:31 ` Andy Shevchenko
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=aG_0K7Zx5WpQHGJE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®