From: Dan Carpenter <dan.carpenter@oracle.com>
To: Martin Kelly <mkelly@xevo.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [bug report] tools: iio: iio_generic_buffer: allow continuous looping
Date: Wed, 9 Jan 2019 09:23:50 +0300 [thread overview]
Message-ID: <20190109062350.GI3253@kadam> (raw)
In-Reply-To: <45679eeb-c078-0253-4131-1cafaf648050@xevo.com>
On Tue, Jan 08, 2019 at 10:20:38PM +0000, Martin Kelly wrote:
> On 1/8/19 12:38 PM, Dan Carpenter wrote:
> > Hello Martin Kelly,
> >
> > The patch 55dda0abcf9d: "tools: iio: iio_generic_buffer: allow
> > continuous looping" from May 17, 2018, leads to the following static
> > checker warning:
> >
> > ./tools/iio/iio_generic_buffer.c:640 main()
> > warn: unsigned 'num_loops' is never less than zero.
> >
>
> Thanks for catching this. How can I repro this so that I can make sure
> the static analyzer is happy once I fix it?
>
It's a Smatch warning. In this case you would just do:
~/path/to/smatch/smatch tools/iio/iio_generic_buffer.c
regards,
dan carpenter
next prev parent reply other threads:[~2019-01-09 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 20:38 [bug report] tools: iio: iio_generic_buffer: allow continuous looping Dan Carpenter
2019-01-08 22:20 ` Martin Kelly
2019-01-09 6:23 ` Dan Carpenter [this message]
2019-01-11 23:03 ` Martin Kelly
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=20190109062350.GI3253@kadam \
--to=dan.carpenter@oracle.com \
--cc=linux-iio@vger.kernel.org \
--cc=mkelly@xevo.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