From: Dan Carpenter <dan.carpenter@oracle.com>
To: cmo@melexis.com
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: [bug report] iio: fetch and enable regulators unconditionally
Date: Wed, 12 Oct 2016 09:07:19 +0300 [thread overview]
Message-ID: <20161012060719.GD12841@mwanda> (raw)
Hello Crt Mori,
The patch 67516074884b: "iio: fetch and enable regulators
unconditionally" from Sep 5, 2016, leads to the following static
checker warning:
drivers/iio/pressure/ms5611_core.c:419 ms5611_init()
error: 'st->vdd' dereferencing possible ERR_PTR()
drivers/iio/pressure/ms5611_core.c
388 static int ms5611_init(struct iio_dev *indio_dev)
389 {
390 int ret;
391 struct ms5611_state *st = iio_priv(indio_dev);
392
393 /* Enable attached regulator if any. */
394 st->vdd = devm_regulator_get(indio_dev->dev.parent, "vdd");
395 if (!IS_ERR(st->vdd)) {
396 ret = regulator_enable(st->vdd);
397 if (ret) {
398 dev_err(indio_dev->dev.parent,
399 "failed to enable Vdd supply: %d\n", ret);
400 return ret;
401 }
402 } else {
403 ret = PTR_ERR(st->vdd);
404 if (ret != -ENODEV)
405 return ret;
You probably want to update this chunk as well? Otherwise static
checkers think we're dereferencing -ENODEV.
406 }
407
408 ret = ms5611_reset(indio_dev);
409 if (ret < 0)
410 goto err_regulator_disable;
411
412 ret = ms5611_read_prom(indio_dev);
413 if (ret < 0)
414 goto err_regulator_disable;
415
416 return 0;
417
418 err_regulator_disable:
419 regulator_disable(st->vdd);
420 return ret;
421 }
regards,
dan carpenter
next reply other threads:[~2016-10-12 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 6:07 Dan Carpenter [this message]
2016-10-13 8:25 ` [bug report] iio: fetch and enable regulators unconditionally Crt Mori
2016-10-14 9:01 ` Lars-Peter Clausen
2016-10-14 11:17 ` Crt Mori
2016-10-14 13:10 ` Linus Walleij
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=20161012060719.GD12841@mwanda \
--to=dan.carpenter@oracle.com \
--cc=cmo@melexis.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