linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: andy.shevchenko@gmail.com
To: Kent Gibson <warthog618@gmail.com>
Cc: Gabriel Matni <gabriel.matni@exfo.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod][PATCH] tools: gpiomon: add timeout option
Date: Tue, 30 May 2023 14:21:18 +0300	[thread overview]
Message-ID: <ZHXcLvUNvw75Z-3W@surfacebook> (raw)
In-Reply-To: <ZHXB83x85Qchv1XJ@sol>

Tue, May 30, 2023 at 05:29:23PM +0800, Kent Gibson kirjoitti:
> On Mon, May 29, 2023 at 08:20:44PM +0000, Gabriel Matni wrote:
> > From: Gabriel Matni <gabriel.matni@exfo.com>

...

> My preferred solution is to run gpiomon as a coproc and have the
> controlling script perform the timeout. e.g.
> 
> #!/bin/env bash

Oh, this is too bad.

> coproc gpiomon "$@"
> while :
> do
>         read -t5 -u ${COPROC[0]} event || break
>         echo $event
> done
> kill $COPROC_PID

I'm wondering what coproc is and why it requires bash.

What I want to have and keep that working is that all our tools can be run in
Busybox environment (embedded application). That's why I'm against seeing bash
in any form of the tooling.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-05-30 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 20:20 [libgpiod][PATCH] tools: gpiomon: add timeout option Gabriel Matni
2023-05-30  9:29 ` Kent Gibson
2023-05-30 11:21   ` andy.shevchenko [this message]
2023-05-30 13:09     ` Kent Gibson
2023-05-30 19:10       ` Bartosz Golaszewski
2023-05-31  1:26         ` Kent Gibson
2023-05-31 13:56           ` [E!] : " Gabriel Matni

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=ZHXcLvUNvw75Z-3W@surfacebook \
    --to=andy.shevchenko@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=gabriel.matni@exfo.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=warthog618@gmail.com \
    /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).