public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Alessandro Zanni <alessandro.zanni87@gmail.com>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	anupnewsmail@gmail.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests/intel_pstate: fix operand expected
Date: Mon, 14 Oct 2024 18:05:57 -0600	[thread overview]
Message-ID: <41d157fc-6413-4061-95af-518ec7b923f1@linuxfoundation.org> (raw)
In-Reply-To: <20241014172149.324639-1-alessandro.zanni87@gmail.com>

On 10/14/24 11:21, Alessandro Zanni wrote:
> This fix solves theses errors, when calling kselftest with
> targets "intel_pstate":
> 
> ./run.sh: line 90: / 1000: syntax error: operand expected (error token is "/ 1000")
> 
> ./run.sh: line 92: / 1000: syntax error: operand expected (error token is "/ 1000")
> 
> To error was found by running tests manually with the command:
> make kselftest TARGETS=intel_pstate
> 
> Signed-off-by: Alessandro Zanni <alessandro.zanni87@gmail.com>
> ---
> 
> Notes:
>      v2: removed debug echos

See my comments on your v1. It would help to wait a bit
to send v2.

I can't reproduce this problem on Linux 6.12-rc3.
What's you environment like?

> 
>   tools/testing/selftests/intel_pstate/run.sh | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/intel_pstate/run.sh b/tools/testing/selftests/intel_pstate/run.sh
> index e7008f614ad7..0c1b6c1308a4 100755
> --- a/tools/testing/selftests/intel_pstate/run.sh
> +++ b/tools/testing/selftests/intel_pstate/run.sh
> @@ -87,9 +87,9 @@ mkt_freq=${_mkt_freq}0
>   
>   # Get the ranges from cpupower
>   _min_freq=$(cpupower frequency-info -l | tail -1 | awk ' { print $1 } ')
> -min_freq=$(($_min_freq / 1000))
> +min_freq=$((_min_freq / 1000))
>   _max_freq=$(cpupower frequency-info -l | tail -1 | awk ' { print $2 } ')
> -max_freq=$(($_max_freq / 1000))
> +max_freq=$((_max_freq / 1000))
>   
>   
>   [ $EVALUATE_ONLY -eq 0 ] && for freq in `seq $max_freq -100 $min_freq`

thanks,
-- Shuah

  reply	other threads:[~2024-10-15  0:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 17:21 [PATCH v2] selftests/intel_pstate: fix operand expected Alessandro Zanni
2024-10-15  0:05 ` Shuah Khan [this message]
2024-10-15 10:20   ` Alessandro Zanni
2024-10-21 15:04     ` Alessandro Zanni
2024-10-21 21:12       ` Shuah Khan
2024-10-21 21:33         ` Alessandro Zanni

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=41d157fc-6413-4061-95af-518ec7b923f1@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=alessandro.zanni87@gmail.com \
    --cc=anupnewsmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox