From: Thomas Gleixner <tglx@linutronix.de>
To: Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
John Stultz <jstultz@google.com>, Stephen Boyd <sboyd@kernel.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 0/3] selftests: timers: Convert some more of the timers tests to KTAP
Date: Thu, 28 Sep 2023 11:49:35 +0200 [thread overview]
Message-ID: <8734yyfx00.ffs@tglx> (raw)
In-Reply-To: <20230927-ktap-posix-timers-v1-0-399de1cbfbea@kernel.org>
On Wed, Sep 27 2023 at 12:18, Mark Brown wrote:
> KTAP is the standard output format for selftests, providing a method for
> systems running the selftests to get results from individual tests
> rather than just a pass/fail for the test program as a whole. While
> many of the timers tests use KTAP some have custom output formats, let's
> convert a few more to KTAP to make them work better in automation.
>
> The posix_timers test made use of perror(), I've added a generic helper
> to kselftest.h for that since it seems like it'll be useful elsewhere.
>
> There are more tests that don't use KTAP, several of them just run a
> single test so don't really benefit from KTAP and there were a couple
> where the conversion was a bit more complex so I've left them for now.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
prev parent reply other threads:[~2023-09-28 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 10:18 [PATCH 0/3] selftests: timers: Convert some more of the timers tests to KTAP Mark Brown
2023-09-27 10:18 ` [PATCH 1/3] kselftest: Add a ksft_perror() helper Mark Brown
2023-09-27 10:18 ` [PATCH 2/3] selftests: timers: Convert posix_timers test to generate KTAP output Mark Brown
2023-09-27 10:18 ` [PATCH 3/3] selftests: timers: Convert nsleep-lat " Mark Brown
2023-09-28 9:49 ` Thomas Gleixner [this message]
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=8734yyfx00.ffs@tglx \
--to=tglx@linutronix.de \
--cc=broonie@kernel.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sboyd@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.