linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Gregor Boirie <gregor.boirie@parrot.com>, linux-iio@vger.kernel.org
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Subject: Re: [PATCH v1 1/1] tools:iio:iio_generic_buffer: fix trigger-less mode
Date: Mon, 29 Aug 2016 18:10:47 +0100	[thread overview]
Message-ID: <72dabc33-f14c-88f8-eb43-819e120e53cb@kernel.org> (raw)
In-Reply-To: <1358a1746e88f7b1bbd6173f1119f39755484ec8.1471946698.git.gregor.boirie@parrot.com>

On 24/08/16 14:28, Gregor Boirie wrote:
> Passing the trigger-less mode option on the command line causes
> iio_generic_buffer to fail searching for an IIO trigger.
> Fix this by skipping trigger initialization if trigger-less mode is
> requested.
> 
> Signed-off-by: Gregor Boirie <gregor.boirie@parrot.com>
Applied to the fixes-togreg branch of iio.git
with an appropriate fixes tag.

Thanks,

Jonathan
> ---
>  tools/iio/iio_generic_buffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/iio/iio_generic_buffer.c b/tools/iio/iio_generic_buffer.c
> index ae68bf0..f39c0e9 100644
> --- a/tools/iio/iio_generic_buffer.c
> +++ b/tools/iio/iio_generic_buffer.c
> @@ -456,7 +456,7 @@ int main(int argc, char **argv)
>  
>  	if (notrigger) {
>  		printf("trigger-less mode selected\n");
> -	} if (trig_num >= 0) {
> +	} else if (trig_num >= 0) {
>  		char *trig_dev_name;
>  		ret = asprintf(&trig_dev_name, "%strigger%d", iio_dir, trig_num);
>  		if (ret < 0) {
> 


      reply	other threads:[~2016-08-29 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 13:28 [PATCH v1 1/1] tools:iio:iio_generic_buffer: fix trigger-less mode Gregor Boirie
2016-08-29 17:10 ` Jonathan Cameron [this message]

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=72dabc33-f14c-88f8-eb43-819e120e53cb@kernel.org \
    --to=jic23@kernel.org \
    --cc=gregor.boirie@parrot.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).