From: Cao Jin <pino.cao2022@gmail.com>
To: Borislav Petkov <bp@alien8.de>, Nathan Chancellor <nathan@kernel.org>
Cc: nsc@kernel.org, linux-kbuild@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] kbuild: improve sanity check for ARCH variable on x86
Date: Mon, 19 Oct 2026 18:26:55 -0700 [thread overview]
Message-ID: <b7720495-5593-43cd-8f59-24bfda39b601@gmail.com> (raw)
In-Reply-To: <20261020005956.GAata9DF4VOpqO71es@fat_crate.local>
Thank you both for prompt response.
I don't think there is document for it, and my rule of thumb tell me
that all of i{3,4,5,6}86 & x86_32 represent 32-bit x86(unless I am
wrong). A young developer may try any of those values at cmdline when
building 32-bit x86 if he doesn't know the nuance among these value.
On 10/19/26 5:59 PM, Borislav Petkov wrote:
> On Mon, Oct 19, 2026 at 05:36:25PM -0700, Nathan Chancellor wrote:
>> On Mon, Oct 19, 2026 at 05:17:38PM -0700, Cao Jin wrote:
>>> When building for x86, ARCH=i{4,5,6}86 and x86_32 will fail the build.
>>
>> Thanks for the patch. Where is it documented that these other options
>> are valid? It seems like this is just expected behavior because these
>> are not valid values for setting ARCH for x86. At the very least, I
>> think something like this needs to be acked by the x86 folks.
>
> I hardly doubt that it'll ever be without a proper explanation why.
>
next prev parent reply other threads:[~2026-10-20 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 0:17 [PATCH] kbuild: improve sanity check for ARCH variable on x86 Cao Jin
2026-10-20 0:36 ` Nathan Chancellor
2026-10-20 0:59 ` Borislav Petkov
2026-10-20 1:26 ` Cao Jin [this message]
2026-10-20 1:33 ` Cao Jin
2026-10-20 1:39 ` Randy Dunlap
2026-10-20 1:38 ` Randy Dunlap
2026-10-20 1:51 ` Cao Jin
2026-10-21 0:17 ` sashiko-bot
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=b7720495-5593-43cd-8f59-24bfda39b601@gmail.com \
--to=pino.cao2022@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.