From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: [PATCH 0/4] kselftest/arm64: Fix compilation warnings/errors in the arm64 tests
Date: Fri, 8 Nov 2024 13:49:16 +0000 [thread overview]
Message-ID: <20241108134920.1233992-1-catalin.marinas@arm.com> (raw)
It looks like people started ignoring the compiler warnings (or even
errors) when building the arm64-specific kselftests. The first three
patches are printf() arguments adjustment. The last one adds
".arch_extension sme", otherwise they fail to build (with my toolchain
versions at least).
Note for future kselftest contributors - try to keep them warning-free.
Catalin Marinas (4):
kselftest/arm64: Fix printf() compiler warnings in the arm64 fp tests
kselftest/arm64: Fix printf() warning in the arm64 MTE prctl() test
kselftest/arm64: Fix printf() compiler warnings in the arm64
syscall-abi.c tests
kselftest/arm64: Fix compilation of SME instructions in the arm64 fp
tests
tools/testing/selftests/arm64/abi/syscall-abi.c | 8 ++++----
tools/testing/selftests/arm64/fp/sve-ptrace.c | 16 +++++++++-------
tools/testing/selftests/arm64/fp/za-ptrace.c | 8 +++++---
tools/testing/selftests/arm64/fp/za-test.S | 1 +
tools/testing/selftests/arm64/fp/zt-ptrace.c | 8 +++++---
tools/testing/selftests/arm64/fp/zt-test.S | 1 +
tools/testing/selftests/arm64/mte/check_prctl.c | 2 +-
7 files changed, 26 insertions(+), 18 deletions(-)
next reply other threads:[~2024-11-08 13:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 13:49 Catalin Marinas [this message]
2024-11-08 13:49 ` [PATCH 1/4] kselftest/arm64: Fix printf() compiler warnings in the arm64 fp tests Catalin Marinas
2024-11-08 15:01 ` Mark Brown
2024-11-08 13:49 ` [PATCH 2/4] kselftest/arm64: Fix printf() warning in the arm64 MTE prctl() test Catalin Marinas
2024-11-08 15:10 ` Mark Brown
2024-11-08 15:25 ` Catalin Marinas
2024-11-08 15:30 ` Mark Brown
2024-11-08 15:35 ` Catalin Marinas
2024-11-08 13:49 ` [PATCH 3/4] kselftest/arm64: Fix printf() compiler warnings in the arm64 syscall-abi.c tests Catalin Marinas
2024-11-08 15:04 ` Mark Brown
2024-11-08 13:49 ` [PATCH 4/4] kselftest/arm64: Fix compilation of SME instructions in the arm64 fp tests Catalin Marinas
2024-11-08 14:53 ` Mark Brown
2024-11-08 14:59 ` Catalin Marinas
2024-11-08 14:58 ` [PATCH 0/4] kselftest/arm64: Fix compilation warnings/errors in the arm64 tests Mark Brown
2024-11-08 15:03 ` Catalin Marinas
2024-11-08 15:16 ` Mark Brown
2024-11-12 16:07 ` (subset) " Catalin Marinas
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=20241108134920.1233992-1-catalin.marinas@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=will@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