From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/1] gpio: add sloppy logic analyzer using polling
Date: Mon, 6 Sep 2021 14:21:26 +0200 [thread overview]
Message-ID: <YTYHxkNdtCA0v244@ninjato> (raw)
In-Reply-To: <CAHp75VdJZhgqshOQS=L1rKiNZLTqNnrc4FXoJKaNpaQT0QB_Eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
> Yes, it means you are not able to use * (a.k.a. glob() function) in
> the shell which increases a lot security and other (misuse) concerns.
> Instead you have to use `find` or similar tools to collect the list of
> the files of your interest.
I see. I don't think this is relevant for the script here, but I'll try
it nonetheless for educational reasons.
> To me it's less error prone to have something like this:
>
> while [ $# -gt 1 ]; do # notice the condition, btw
> case "$1" in
> opt_with_parameter) ...; shift;;
> toggler_opt) ...;;
> esac
> shift
> done
Ok, I like it. Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-06 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 19:45 [PATCH 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2021-09-01 19:45 ` [PATCH 1/1] gpio: add sloppy " Wolfram Sang
2021-09-05 11:20 ` Andy Shevchenko
2021-09-06 9:04 ` Wolfram Sang
2021-09-06 10:15 ` Andy Shevchenko
2021-09-06 12:21 ` Wolfram Sang [this message]
[not found] ` <CAHp75VdNnvUfMEL3gMrJOFix3AATL8LAiU18LXJJVL77feBRow@mail.gmail.com>
2021-09-06 7:38 ` Wolfram Sang
2021-09-06 7:47 ` Andy Shevchenko
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=YTYHxkNdtCA0v244@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andy.shevchenko@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@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