From: Muhammad Usama Anjum <usama.anjum@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: usama.anjum@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shuah Khan <shuah@kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Yeoreum Yun <yeoreum.yun@arm.com>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2 2/5] selftests/arm64: Print missing MTE TAP headers
Date: Fri, 21 Aug 2026 17:11:28 +0100 [thread overview]
Message-ID: <dd3e1cec-1177-4b34-946e-20f0cfeaff7b@arm.com> (raw)
In-Reply-To: <b95d6b82-ce25-4d89-8d8e-8be1f111812f@sirena.org.uk>
On 21/08/2026 5:04 pm, Mark Brown wrote:
> On Fri, Aug 21, 2026 at 03:15:50PM +0100, Muhammad Usama Anjum wrote:
>> Most of the remaining MTE tests set a TAP plan and emit results without
>> first printing the TAP version header. Direct execution therefore starts
>> with a plan such as "1..20" instead of "TAP version 13".
>>
>> Print the header in every remaining MTE test that is missing it. Do so
>> before setup and prerequisite checks so early failures and whole-test
>> skips also retain the header.
>>
>> Signed-off-by: Muhammad Usama Anjum <usama.anjum@arm.com>
>> ---
>> Newly introduced. This is an output-format consistency change and does
>> not fix duplicated output or alter test execution behavior.
>
> This should probably just be a single patch with patch 1.
My idea here is that the first patch would get backported as that's
true logs cleanup patch. (1024 lines of 1..1 are avoided with that).
This patch wouldn't get backported. Its just formatting fixing of the
output.
--
Thanks,
Usama
next prev parent reply other threads:[~2026-08-21 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 14:15 [PATCH v2 0/5] selftest/arm64: Fix MTE test setup and TAP reporting Muhammad Usama Anjum
2026-08-21 14:15 ` [PATCH v2 1/5] selftests/arm64: Print TAP header Muhammad Usama Anjum
2026-08-21 14:15 ` [PATCH v2 2/5] selftests/arm64: Print missing MTE TAP headers Muhammad Usama Anjum
2026-08-21 16:04 ` Mark Brown
2026-08-21 16:11 ` Muhammad Usama Anjum [this message]
2026-08-21 16:21 ` Mark Brown
2026-08-25 10:21 ` Muhammad Usama Anjum
2026-08-21 14:15 ` [PATCH v2 3/5] selftests/arm64: Treat KSM merge_across_nodes as optional Muhammad Usama Anjum
2026-08-21 15:43 ` Mark Brown
2026-08-21 15:56 ` Muhammad Usama Anjum
2026-08-21 14:15 ` [PATCH v2 4/5] selftests/arm64: Fix MTE prctl TAP plan Muhammad Usama Anjum
2026-08-21 14:15 ` [PATCH v2 5/5] selftests/arm64: Add MTE test config fragment Muhammad Usama Anjum
2026-08-21 16:07 ` Mark Brown
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=dd3e1cec-1177-4b34-946e-20f0cfeaff7b@arm.com \
--to=usama.anjum@arm.com \
--cc=akpm@linux-foundation.org \
--cc=amit.kachhap@arm.com \
--cc=andreyknvl@gmail.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.com \
/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