From: Colin King <colin.king@canonical.com> To: "Jonathan Cameron" <jic23@kernel.org>, "Hartmut Knaack" <knaack.h@gmx.de>, "Lars-Peter Clausen" <lars@metafoo.de>, "Peter Meerwald-Stadler" <pmeerw@pmeerw.net>, "Stefan Brüns" <stefan.bruens@rwth-aachen.de>, linux-iio@vger.kernel.org Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] iio: adc: ina2xx: fix missing break statement Date: Mon, 8 Oct 2018 22:09:04 +0100 [thread overview] Message-ID: <20181008210904.9362-1-colin.king@canonical.com> (raw) From: Colin Ian King <colin.king@canonical.com> The IIO_CHAN_INFO_SCALE case is missing a break statement and in the unlikely event that chan->address is not matched in the nested switch statement then the code falls through to the following IIO_CHAN_INFO_HARDWAREGAIN case. Fix this by adding the missing break. While we are fixing this, it's probably a good idea to add in a break statement to the IIO_CHAN_INFO_HARDWAREGAIN case too (this is a moot point). Detected by CoverityScan, CID#1462408 ("Missing break in switch") Fixes: ca6a2d86acae ("iio: adc: ina2xx: Allow setting Shunt Voltage PGA gain and Bus Voltage range") Signed-off-by: Colin Ian King <colin.king@canonical.com> --- drivers/iio/adc/ina2xx-adc.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/iio/adc/ina2xx-adc.c b/drivers/iio/adc/ina2xx-adc.c index d1239624187d..9bc5986780b9 100644 --- a/drivers/iio/adc/ina2xx-adc.c +++ b/drivers/iio/adc/ina2xx-adc.c @@ -250,6 +250,7 @@ static int ina2xx_read_raw(struct iio_dev *indio_dev, *val2 = chip->shunt_resistor_uohm; return IIO_VAL_FRACTIONAL; } + break; case IIO_CHAN_INFO_HARDWAREGAIN: switch (chan->address) { @@ -262,6 +263,7 @@ static int ina2xx_read_raw(struct iio_dev *indio_dev, *val = chip->range_vbus == 32 ? 1 : 2; return IIO_VAL_INT; } + break; } return -EINVAL; -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Colin King <colin.king@canonical.com> To: "Jonathan Cameron" <jic23@kernel.org>, "Hartmut Knaack" <knaack.h@gmx.de>, "Lars-Peter Clausen" <lars@metafoo.de>, "Peter Meerwald-Stadler" <pmeerw@pmeerw.net>, "Stefan Brüns" <stefan.bruens@rwth-aachen.de>, linux-iio@vger.kernel.org Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] iio: adc: ina2xx: fix missing break statement Date: Mon, 08 Oct 2018 21:09:04 +0000 [thread overview] Message-ID: <20181008210904.9362-1-colin.king@canonical.com> (raw) From: Colin Ian King <colin.king@canonical.com> The IIO_CHAN_INFO_SCALE case is missing a break statement and in the unlikely event that chan->address is not matched in the nested switch statement then the code falls through to the following IIO_CHAN_INFO_HARDWAREGAIN case. Fix this by adding the missing break. While we are fixing this, it's probably a good idea to add in a break statement to the IIO_CHAN_INFO_HARDWAREGAIN case too (this is a moot point). Detected by CoverityScan, CID#1462408 ("Missing break in switch") Fixes: ca6a2d86acae ("iio: adc: ina2xx: Allow setting Shunt Voltage PGA gain and Bus Voltage range") Signed-off-by: Colin Ian King <colin.king@canonical.com> --- drivers/iio/adc/ina2xx-adc.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/iio/adc/ina2xx-adc.c b/drivers/iio/adc/ina2xx-adc.c index d1239624187d..9bc5986780b9 100644 --- a/drivers/iio/adc/ina2xx-adc.c +++ b/drivers/iio/adc/ina2xx-adc.c @@ -250,6 +250,7 @@ static int ina2xx_read_raw(struct iio_dev *indio_dev, *val2 = chip->shunt_resistor_uohm; return IIO_VAL_FRACTIONAL; } + break; case IIO_CHAN_INFO_HARDWAREGAIN: switch (chan->address) { @@ -262,6 +263,7 @@ static int ina2xx_read_raw(struct iio_dev *indio_dev, *val = chip->range_vbus = 32 ? 1 : 2; return IIO_VAL_INT; } + break; } return -EINVAL; -- 2.17.1
next reply other threads:[~2018-10-08 21:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-08 21:09 Colin King [this message] 2018-10-08 21:09 ` [PATCH] iio: adc: ina2xx: fix missing break statement Colin King 2018-10-10 7:51 ` Matt Ranostay 2018-10-10 7:51 ` Matt Ranostay 2018-10-10 7:59 ` Colin Ian King 2018-10-10 7:59 ` Colin Ian King 2018-10-10 10:42 ` Stefan Brüns 2018-10-10 10:42 ` Stefan Brüns 2018-10-13 12:44 ` Jonathan Cameron 2018-10-13 12:44 ` Jonathan Cameron 2018-10-13 12:44 ` Jonathan Cameron
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=20181008210904.9362-1-colin.king@canonical.com \ --to=colin.king@canonical.com \ --cc=jic23@kernel.org \ --cc=kernel-janitors@vger.kernel.org \ --cc=knaack.h@gmx.de \ --cc=lars@metafoo.de \ --cc=linux-iio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=pmeerw@pmeerw.net \ --cc=stefan.bruens@rwth-aachen.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.