From: Will Deacon <will@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Shuah Khan <shuah@kernel.org>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Mark Brown <broonie@kernel.org>,
linux-kselftest@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kselftest/arm64: build BTI tests in output directory
Date: Wed, 16 Aug 2023 19:25:23 +0100 [thread overview]
Message-ID: <169219342837.1947103.11802774487228057167.b4-ty@kernel.org> (raw)
In-Reply-To: <20230815145931.2522557-1-andre.przywara@arm.com>
On Tue, 15 Aug 2023 15:59:31 +0100, Andre Przywara wrote:
> The arm64 BTI selftests are currently built in the source directory,
> then the generated binaries are copied to the output directory.
> This leaves the object files around in a potentially otherwise pristine
> source tree, tainting it for out-of-tree kernel builds.
>
> Prepend $(OUTPUT) to every reference to an object file in the Makefile,
> and remove the extra handling and copying. This puts all generated files
> under the output directory.
>
> [...]
Applied to arm64 (for-next/selftests), thanks!
[1/1] kselftest/arm64: build BTI tests in output directory
https://git.kernel.org/arm64/c/e08302ee46c9
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Shuah Khan <shuah@kernel.org>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Mark Brown <broonie@kernel.org>,
linux-kselftest@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kselftest/arm64: build BTI tests in output directory
Date: Wed, 16 Aug 2023 19:25:23 +0100 [thread overview]
Message-ID: <169219342837.1947103.11802774487228057167.b4-ty@kernel.org> (raw)
In-Reply-To: <20230815145931.2522557-1-andre.przywara@arm.com>
On Tue, 15 Aug 2023 15:59:31 +0100, Andre Przywara wrote:
> The arm64 BTI selftests are currently built in the source directory,
> then the generated binaries are copied to the output directory.
> This leaves the object files around in a potentially otherwise pristine
> source tree, tainting it for out-of-tree kernel builds.
>
> Prepend $(OUTPUT) to every reference to an object file in the Makefile,
> and remove the extra handling and copying. This puts all generated files
> under the output directory.
>
> [...]
Applied to arm64 (for-next/selftests), thanks!
[1/1] kselftest/arm64: build BTI tests in output directory
https://git.kernel.org/arm64/c/e08302ee46c9
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2023-08-16 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 14:59 [PATCH] kselftest/arm64: build BTI tests in output directory Andre Przywara
2023-08-15 14:59 ` Andre Przywara
2023-08-16 13:30 ` Mark Brown
2023-08-16 13:30 ` Mark Brown
2023-08-16 18:25 ` Will Deacon [this message]
2023-08-16 18:25 ` Will Deacon
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=169219342837.1947103.11802774487228057167.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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.