From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH v1 1/3] kselftest/arm64: Add missing newline in hwcap output
Date: Tue, 13 Sep 2022 15:10:59 +0100 [thread overview]
Message-ID: <20220913141101.151400-2-broonie@kernel.org> (raw)
In-Reply-To: <20220913141101.151400-1-broonie@kernel.org>
Clean up the output of the test by adding a missing newline, the fix had
been done locally but didn't make it into the applied version.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/arm64/abi/hwcap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/arm64/abi/hwcap.c b/tools/testing/selftests/arm64/abi/hwcap.c
index 8b5c646cea63..04e4a81dd159 100644
--- a/tools/testing/selftests/arm64/abi/hwcap.c
+++ b/tools/testing/selftests/arm64/abi/hwcap.c
@@ -151,7 +151,7 @@ int main(void)
have_cpuinfo = cpuinfo_present(hwcap->cpuinfo);
if (have_hwcap)
- ksft_print_msg("%s present", hwcap->name);
+ ksft_print_msg("%s present\n", hwcap->name);
ksft_test_result(have_hwcap == have_cpuinfo,
"cpuinfo_match_%s\n", hwcap->name);
--
2.30.2
next prev parent reply other threads:[~2022-09-13 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 14:10 [PATCH v1 0/3] kselftest/arm64: Updates to the hwcaps test Mark Brown
2022-09-13 14:10 ` Mark Brown [this message]
2022-09-13 14:11 ` [PATCH v1 2/3] kselftest/arm64: Add SVE 2 to the tested hwcaps Mark Brown
2022-09-13 14:11 ` [PATCH v1 3/3] kselftest/arm64: Add hwcap test for RNG Mark Brown
2022-09-16 17:46 ` [PATCH v1 0/3] kselftest/arm64: Updates to the hwcaps test 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=20220913141101.151400-2-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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