From: Kees Cook <kees@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
"Bird, Timothy" <Tim.Bird@sony.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] selftests/timens: Print TAP headers
Date: Fri, 9 May 2025 12:07:28 -0700 [thread overview]
Message-ID: <202505091206.B4DD09AB27@keescook> (raw)
In-Reply-To: <20250509172639-61bade20-67f9-4815-8316-1bb16749f8d9@linutronix.de>
On Fri, May 09, 2025 at 05:41:03PM +0200, Thomas Weißschuh wrote:
> The suppression was actually there at some point and got removed by Kees in
> commit f41c322f17ec ("selftests: Remove KSFT_TAP_LEVEL").
Right, to get consistent output and to work with indentation, there's no
need to track level any more.
If you want to be able to explicitly supress KTAP output, that's
probably a new thing to be added. But normally it's not needed -- things
should be fairly readable even with KTAP output.
--
Kees Cook
next prev parent reply other threads:[~2025-05-09 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 12:03 [PATCH 0/3] selftests/timens: Various small fixes Thomas Weißschuh
2025-05-02 12:03 ` [PATCH 1/3] selftests/timens: Print TAP headers Thomas Weißschuh
2025-05-02 12:13 ` Muhammad Usama Anjum
2025-05-07 21:06 ` Shuah Khan
2025-05-09 15:41 ` Thomas Weißschuh
2025-05-09 18:53 ` Shuah Khan
2025-05-09 19:07 ` Kees Cook [this message]
2025-05-02 12:03 ` [PATCH 2/3] selftests/timens: Make run_tests() functions static Thomas Weißschuh
2025-05-02 12:13 ` Muhammad Usama Anjum
2025-05-02 12:03 ` [PATCH 3/3] selftests/timens: timerfd: Use correct clockid type in tclock_gettime() Thomas Weißschuh
2025-05-02 12:14 ` Muhammad Usama Anjum
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=202505091206.B4DD09AB27@keescook \
--to=kees@kernel.org \
--cc=Tim.Bird@sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
/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