mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>, Kees Cook <kees@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Bill Wendling" <morbo@google.com>,
	"Justin Stitt" <justinstitt@google.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
	"David Gow" <davidgow@google.com>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2] kbuild: clang: Support building UM with SUBARCH=i386
Date: Tue,  4 Mar 2025 09:50:34 -0800	[thread overview]
Message-ID: <174111063359.3934820.5690548067195753148.b4-ty@kernel.org> (raw)
In-Reply-To: <20250304162124.it.785-kees@kernel.org>

On Tue, 04 Mar 2025 08:21:29 -0800, Kees Cook wrote:
> The UM builds distinguish i386 from x86_64 via SUBARCH, but we don't
> support building i386 directly with Clang. To make SUBARCH work for
> i386 UM, we need to explicitly test for it.
> 
> This lets me run i386 KUnit tests with Clang:
> 
> $ ./tools/testing/kunit/kunit.py run \
> 	--make_options LLVM=1 \
> 	--make_options SUBARCH=i386
> ...
> 
> [...]

Applied to for-next/hardening, thanks!

[1/1] kbuild: clang: Support building UM with SUBARCH=i386
      https://git.kernel.org/kees/c/a48d9ebdbb5a

Take care,

-- 
Kees Cook


  parent reply	other threads:[~2025-03-04 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 16:21 Kees Cook
2025-03-04 16:28 ` Nathan Chancellor
2025-03-04 17:50 ` Kees Cook [this message]
2025-03-06  8:59 ` David Gow
2025-03-07  3:41   ` Kees Cook

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=174111063359.3934820.5690548067195753148.b4-ty@kernel.org \
    --to=kees@kernel.org \
    --cc=davidgow@google.com \
    --cc=justinstitt@google.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    /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®