Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Cao Jin <pino.cao2022@gmail.com>
To: 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:33:59 -0700	[thread overview]
Message-ID: <3f05fea2-7843-4738-9d58-b245645791ab@gmail.com> (raw)
In-Reply-To: <20261020003625.GA787785@ax162>



On 10/19/26 5:36 PM, 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.
> 

Forget to mention, "i386" & "x86_64" are not valid value for ARCH for 
x86 either, the top Makefile correct them to "x86". So we may want to 
correct all other possible invalid value for x86 ARCH, if my 
understanding of i{3,4,5,6}86 are the same for 32-bit x86 were right.


  parent reply	other threads:[~2026-10-20  1:34 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
2026-10-20  1:33   ` Cao Jin [this message]
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=3f05fea2-7843-4738-9d58-b245645791ab@gmail.com \
    --to=pino.cao2022@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox