From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Kunwu Chan <chentao@kylinos.cn>,
kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] selftests: arm64: tags_test: conform test to TAP output
Date: Wed, 10 Jul 2024 14:10:53 +0100 [thread overview]
Message-ID: <Zo6IXQM-R_1YJGIn@finisterre.sirena.org.uk> (raw)
In-Reply-To: <Zo5xCW9GJqFeTZUi@arm.com>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Wed, Jul 10, 2024 at 12:31:21PM +0100, Catalin Marinas wrote:
> Sorry, these patches slipped through the cracks. We seem to be pretty
> inconsistent with using ksft_exit_fail_perror() and ksft_finished(). Is
> there some plan to update the rest or is it only this location that you
> came across?
Any ksft_exit_*() should implicitly do a ksft_finished(), the _exit_
will just exit the test program immediately. ksft_finished() is for
normal exit from the test program after running everything.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-10 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 13:24 [PATCH 1/2] selftests: arm64: tags_test: conform test to TAP output Muhammad Usama Anjum
2024-06-02 13:25 ` [PATCH 2/2] selftests: arm64: tags: remove the result script Muhammad Usama Anjum
2024-07-01 8:40 ` [PATCH 1/2] selftests: arm64: tags_test: conform test to TAP output Muhammad Usama Anjum
2024-07-10 9:35 ` Muhammad Usama Anjum
2024-07-10 11:31 ` Catalin Marinas
2024-07-10 13:10 ` Mark Brown [this message]
2024-07-11 6:13 ` Muhammad Usama Anjum
2024-07-11 18:48 ` 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=Zo6IXQM-R_1YJGIn@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chentao@kylinos.cn \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
--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