Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
	"Shuah Khan" <shuah@kernel.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Sebastian Reichel <sre@kernel.org>,
	Mike Looijmans <mike.looijmans@topic.nl>,
	kernel@collabora.com, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] selftests: ktap_helpers: Make it POSIX-compliant
Date: Mon, 15 Apr 2024 23:38:20 +0500	[thread overview]
Message-ID: <732fb6c2-230d-4d48-8ecc-dba6c1688142@collabora.com> (raw)
In-Reply-To: <20240415-supply-selftest-posix-sh-v1-1-328f008d698d@collabora.com>

On 4/15/24 8:32 PM, Nícolas F. R. A. Prado wrote:
> There are a couple uses of bash specific syntax in the script. Change
> them to the equivalent POSIX syntax. This doesn't change functionality
> and allows non-bash test scripts to make use of these helpers.
> 
> Reported-by: Mike Looijmans <mike.looijmans@topic.nl>
> Closes: https://lore.kernel.org/all/efae4037-c22a-40be-8ba9-7c1c12ece042@topic.nl/
> Fixes: 2dd0b5a8fcc4 ("selftests: ktap_helpers: Add a helper to finish the test")
> Fixes: 14571ab1ad21 ("kselftest: Add new test for detecting unprobed Devicetree devices")
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>

> ---
>  tools/testing/selftests/kselftest/ktap_helpers.sh | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/kselftest/ktap_helpers.sh b/tools/testing/selftests/kselftest/ktap_helpers.sh
> index f2fbb914e058..79a125eb24c2 100644
> --- a/tools/testing/selftests/kselftest/ktap_helpers.sh
> +++ b/tools/testing/selftests/kselftest/ktap_helpers.sh
> @@ -43,7 +43,7 @@ __ktap_test() {
>  	directive="$3" # optional
>  
>  	local directive_str=
> -	[[ ! -z "$directive" ]] && directive_str="# $directive"
> +	[ ! -z "$directive" ] && directive_str="# $directive"
>  
>  	echo $result $KTAP_TESTNO $description $directive_str
>  
> @@ -99,7 +99,7 @@ ktap_exit_fail_msg() {
>  ktap_finished() {
>  	ktap_print_totals
>  
> -	if [ $(("$KTAP_CNT_PASS" + "$KTAP_CNT_SKIP")) -eq "$KSFT_NUM_TESTS" ]; then
> +	if [ $((KTAP_CNT_PASS + KTAP_CNT_SKIP)) -eq "$KSFT_NUM_TESTS" ]; then
>  		exit "$KSFT_PASS"
>  	else
>  		exit "$KSFT_FAIL"
> 

-- 
BR,
Muhammad Usama Anjum

  reply	other threads:[~2024-04-15 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 15:32 [PATCH 0/2] selftests: Make sh helper and power supply test POSIX-compliant Nícolas F. R. A. Prado
2024-04-15 15:32 ` [PATCH 1/2] selftests: ktap_helpers: Make it POSIX-compliant Nícolas F. R. A. Prado
2024-04-15 18:38   ` Muhammad Usama Anjum [this message]
2024-04-15 15:32 ` [PATCH 2/2] selftests: power_supply: " Nícolas F. R. A. Prado
2024-04-15 18:38   ` Muhammad Usama Anjum
2024-04-24 13:33 ` [PATCH 0/2] selftests: Make sh helper and power supply test POSIX-compliant 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=732fb6c2-230d-4d48-8ecc-dba6c1688142@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    --cc=nfraprado@collabora.com \
    --cc=shuah@kernel.org \
    --cc=sre@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