From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>, Sasha Levin <sashal@kernel.org>
Cc: "Shuah Khan" <shuah@kernel.org>,
"Ricardo B. Marlière" <rbm@suse.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH 1/7] selftests: keep the build status from wrapping to success
Date: Thu, 15 Oct 2026 13:21:53 -0600 [thread overview]
Message-ID: <d7550cd1-e0fe-4e85-8a93-c2bf4c789e59@linuxfoundation.org> (raw)
In-Reply-To: <f64e8221-cedb-4b4e-aed4-a87ac23c26cf@sirena.org.uk>
On 10/15/26 12:00, Mark Brown wrote:
> On Wed, Oct 14, 2026 at 04:01:09PM -0400, Sasha Levin wrote:
>
>> Record a successful target instead of multiplying statuses. The rules
>> still fail only when no target succeeds, and FORCE_TARGETS still stops
>> at the first failure.
>
> Reviewed-by: Mark Brown <broonie@kernel.org>
Thank you both. Applied to kselftest next for 7.4-rc1
thanks,
-- Shuah
next prev parent reply other threads:[~2026-10-15 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 20:01 [PATCH 0/7] selftests: report per-suite build results without failing the build Sasha Levin
2026-10-14 20:01 ` Sasha Levin
2026-10-14 20:01 ` [PATCH 1/7] selftests: keep the build status from wrapping to success Sasha Levin
2026-10-15 18:00 ` Mark Brown
2026-10-15 19:21 ` Shuah Khan [this message]
2026-10-14 20:01 ` [PATCH 2/7] selftests: optionally record per-suite build and install results Sasha Levin
2026-10-15 19:22 ` Shuah Khan
2026-10-14 20:01 ` [PATCH 3/7] selftests/futex: report failures of the functional subdirectory Sasha Levin
2026-10-14 20:01 ` [PATCH 4/7] kselftest/arm64: keep building and installing after a subdirectory fails Sasha Levin
2026-10-15 17:46 ` Catalin Marinas
2026-10-15 18:16 ` Mark Brown
2026-10-14 20:01 ` [PATCH 5/7] selftests/riscv: " Sasha Levin
2026-10-14 20:01 ` Sasha Levin
2026-10-14 20:01 ` [PATCH 6/7] selftests/powerpc: report the outcome of each subdirectory Sasha Levin
2026-10-14 20:01 ` [PATCH 7/7] selftests/sparc64: report failures of the drivers subdirectory Sasha Levin
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=d7550cd1-e0fe-4e85-8a93-c2bf4c789e59@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rbm@suse.com \
--cc=sashal@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.