From: Tomasz Duszynski <tduszyns@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, Andreas Brauchli <a.brauchli@elementarea.net>
Subject: Re: [PATCH] iio:chemical:sps30 Suppress some switch fallthrough warnings.
Date: Sat, 9 Feb 2019 21:12:10 +0100 [thread overview]
Message-ID: <20190209201209.GA19661@arch> (raw)
In-Reply-To: <20190209193934.64038cf4@archlinux>
On Sat, Feb 09, 2019 at 07:39:34PM +0000, Jonathan Cameron wrote:
> Fixes warnings reported on linux-next but marking one path
> and adding an explicit return in the other.
>
Looks good.
Acked-by: Tomasz Duszynski <tduszyns@gmail.com>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Andreas Brauchli <a.brauchli@elementarea.net>
> ---
> I'd like to get this one into linux-next fairly quick so it anyone
> has time to do a quick sanity check it would be much appreciated!
>
> drivers/iio/chemical/sps30.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/chemical/sps30.c b/drivers/iio/chemical/sps30.c
> index 375df5060ed5..edbb956e81e8 100644
> --- a/drivers/iio/chemical/sps30.c
> +++ b/drivers/iio/chemical/sps30.c
> @@ -118,6 +118,7 @@ static int sps30_do_cmd(struct sps30_state *state, u16 cmd, u8 *data, int size)
> case SPS30_READ_AUTO_CLEANING_PERIOD:
> buf[0] = SPS30_AUTO_CLEANING_PERIOD >> 8;
> buf[1] = (u8)SPS30_AUTO_CLEANING_PERIOD;
> + /* fall through */
> case SPS30_READ_DATA_READY_FLAG:
> case SPS30_READ_DATA:
> case SPS30_READ_SERIAL:
> @@ -295,6 +296,8 @@ static int sps30_read_raw(struct iio_dev *indio_dev,
> *val2 = 10000;
>
> return IIO_VAL_INT_PLUS_MICRO;
> + default:
> + return -EINVAL;
> }
> default:
> return -EINVAL;
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-02-09 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 19:39 [PATCH] iio:chemical:sps30 Suppress some switch fallthrough warnings Jonathan Cameron
2019-02-09 20:12 ` Tomasz Duszynski [this message]
2019-02-11 20:08 ` 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=20190209201209.GA19661@arch \
--to=tduszyns@gmail.com \
--cc=a.brauchli@elementarea.net \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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