From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH libgpiod 2/4] tools: tests: use $@ instead of $*
Date: Sat, 25 May 2024 09:54:31 +0800 [thread overview]
Message-ID: <20240525015431.GA5731@rigel> (raw)
In-Reply-To: <20240524-fix-bash-tests-v1-2-1397c73073a6@linaro.org>
On Fri, May 24, 2024 at 08:03:28PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> $@ does not break up quoted arguments which is what we want in all cases
> in the bash test-suite. Use it instead of $*.
>
I believe it needs to be "$@". Everywhere.
Where do we use quoted arguments/whitespaced parameters?
So this is purely about "good" shell? In that case why stop here - e.g.
shellcheck picks up a load more "Double quote to prevent splitting/globbing"
and the like.
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> tools/gpio-tools-test.bash | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/tools/gpio-tools-test.bash b/tools/gpio-tools-test.bash
> index abb2f5d..8b4f054 100755
> --- a/tools/gpio-tools-test.bash
> +++ b/tools/gpio-tools-test.bash
> @@ -27,10 +27,10 @@ GPIOSIM_APP_NAME="gpio-tools-test"
> MIN_KERNEL_VERSION="5.17.4"
> MIN_SHUNIT_VERSION="2.1.8"
>
> -# Run the command in $* and fail the test if the command succeeds.
> +# Run the command in $@ and fail the test if the command succeeds.
> assert_fail() {
> - $* || return 0
> - fail " '$*': command did not fail as expected"
> + $@ || return 0
> + fail " '$@': command did not fail as expected"
> }
>
> # Check if the string in $2 matches against the pattern in $1.
> @@ -71,7 +71,7 @@ gpiosim_chip() {
>
> mkdir -p $BANKPATH
>
> - for ARG in $*
> + for ARG in $@
> do
> local KEY=$(echo $ARG | cut -d"=" -f1)
> local VAL=$(echo $ARG | cut -d"=" -f2)
> @@ -253,7 +253,7 @@ dut_regex_match() {
> }
>
> dut_write() {
> - echo $* >&${COPROC[1]}
> + echo $@ >&${COPROC[1]}
> }
>
Does echo care? I realise a linter, and that includes Andy, will complain
here, but is there a practical difference?
Cheers,
Kent.
> dut_kill() {
> @@ -283,7 +283,7 @@ tearDown() {
> }
>
> request_release_line() {
> - $SOURCE_DIR/gpioget -c $* >/dev/null
> + $SOURCE_DIR/gpioget -c $@ >/dev/null
> }
>
> #
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-05-25 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 18:03 [PATCH libgpiod 0/4] tools: tests: fix a few issues in bash scripts Bartosz Golaszewski
2024-05-24 18:03 ` [PATCH libgpiod 1/4] tools: tests: use tabs for indentation consistently Bartosz Golaszewski
2024-05-24 18:03 ` [PATCH libgpiod 2/4] tools: tests: use $@ instead of $* Bartosz Golaszewski
2024-05-25 1:54 ` Kent Gibson [this message]
2024-05-27 9:49 ` Bartosz Golaszewski
2024-05-27 10:24 ` Kent Gibson
2024-05-27 11:37 ` Bartosz Golaszewski
2024-05-24 18:03 ` [PATCH libgpiod 3/4] tools: tests: remove unneeded ';' in while loops Bartosz Golaszewski
2024-05-24 18:03 ` [PATCH libgpiod 4/4] tools: tests: remove dependency on grep Bartosz Golaszewski
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=20240525015431.GA5731@rigel \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.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;
as well as URLs for NNTP newsgroup(s).