From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "Ricardo B. Marlière" <rbm@suse.com>,
torvalds@linux-foundation.org, "Shuah Khan" <shuah@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, Aishwarya.TCV@arm.com,
ben.copeland@linaro.org, kernelci@lists.linux.dev
Subject: Re: [PATCH 5/6] selftests: Preserve subtarget failures in all/install
Date: Fri, 17 Apr 2026 14:30:40 +0100 [thread overview]
Message-ID: <e54a02b1-dd0b-4dd4-93aa-0484bb2cd8fe@sirena.org.uk> (raw)
In-Reply-To: <0420ebf1-2598-4f4f-bd09-95774156b48b@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Thu, Apr 16, 2026 at 03:15:30PM -0600, Shuah Khan wrote:
> Just a quick note to say I applied all 3 patches and will send pr tomorrow.
Confirmed that everything seems to be running fine in -next for me. I
am seeing the test number duplicated in the log messages from the
wrapper:
ok 59 59 selftests: arm64: syscall-abi
which is confusing my parser a little but is less of an emergency, I'll
take a look.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-17 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260320-selftests-fixes-v1-0-79144f76be01@suse.com>
[not found] ` <20260320-selftests-fixes-v1-5-79144f76be01@suse.com>
2026-04-15 13:58 ` [PATCH 5/6] selftests: Preserve subtarget failures in all/install Mark Brown
2026-04-15 15:40 ` Shuah Khan
2026-04-15 15:42 ` Ricardo B. Marlière
2026-04-15 15:52 ` Shuah Khan
2026-04-15 15:53 ` Ricardo B. Marlière
2026-04-15 16:25 ` Mark Brown
2026-04-15 16:39 ` Shuah Khan
2026-04-16 13:16 ` Mark Brown
2026-04-16 15:08 ` Shuah Khan
2026-04-16 15:15 ` Mark Brown
2026-04-16 15:21 ` Shuah Khan
2026-04-16 21:15 ` Shuah Khan
2026-04-17 10:36 ` Mark Brown
2026-04-17 13:30 ` Mark Brown [this message]
2026-04-17 17:27 ` Shuah Khan
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=e54a02b1-dd0b-4dd4-93aa-0484bb2cd8fe@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=ben.copeland@linaro.org \
--cc=kernelci@lists.linux.dev \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=rbm@suse.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=torvalds@linux-foundation.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