public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Hangbin Liu <liuhangbin@gmail.com>,
	Brendan Jackman <jackmanb@google.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2] selftests: Fix runner.sh breakage
Date: Thu, 16 Apr 2026 15:14:44 -0600	[thread overview]
Message-ID: <e138bae2-3a3c-4183-8f2c-5768a2bfe2f0@linuxfoundation.org> (raw)
In-Reply-To: <20260416-selftest-fix-readlink-e-v1-0-94e4cabbdec4@kernel.org>

On 4/16/26 13:03, Mark Brown wrote:
> Commit 2964f6b816c2 ("selftests: Use ktap helpers for runner.sh")
> introduced several regressions by introducing dependencies on bash and
> GNU coreutils breaking testing on Debian based systems.  Roll these
> changes back.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Mark Brown (2):
>        selftests: Fix runner.sh busybox support
>        selftests: Fix runner.sh for non-bash shells
> 
>   tools/testing/selftests/kselftest/runner.sh | 26 ++++++++++++++------------
>   1 file changed, 14 insertions(+), 12 deletions(-)
> ---
> base-commit: 2964f6b816c25ee094df4a143eb5b8828910045f
> change-id: 20260416-selftest-fix-readlink-e-da604f02686b
> 
> Best regards,
> --
> Mark Brown <broonie@kernel.org>
> 

Thank you. I applied these two patches to linux-kselftest next and will send pr tomorrow.

thanks,
-- Shuah

      parent reply	other threads:[~2026-04-16 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 19:03 [PATCH 0/2] selftests: Fix runner.sh breakage Mark Brown
2026-04-16 19:03 ` [PATCH 1/2] selftests: Fix runner.sh busybox support Mark Brown
2026-04-16 19:03 ` [PATCH 2/2] selftests: Fix runner.sh for non-bash shells Mark Brown
2026-04-16 21:14 ` Shuah Khan [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=e138bae2-3a3c-4183-8f2c-5768a2bfe2f0@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox