From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: dummy: events: Add missing break
Date: Sun, 1 Oct 2017 11:17:56 +0100 [thread overview]
Message-ID: <20171001111756.057b80f1@archlinux> (raw)
In-Reply-To: <20170929132405.28104-1-lars@metafoo.de>
On Fri, 29 Sep 2017 15:24:05 +0200
Lars-Peter Clausen <lars@metafoo.de> wrote:
> Add missing break in iio_simple_dummy_write_event_config() for the voltage
> threshold event enable attribute. Without this writing to the
> in_voltage0_thresh_rising_en always returns -EINVAL even though the change
> was correctly applied.
>
> Fixes: 3e34e650db197 ("iio: dummy: Demonstrate the usage of new channel types")
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Applied to the fixes-togreg branch of iio.git and marked for stable.
It's hardly a critical stable fix, but the risk is obviously very low
as well ;)
Thanks,
Jonathan
> ---
> drivers/iio/dummy/iio_simple_dummy_events.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/dummy/iio_simple_dummy_events.c b/drivers/iio/dummy/iio_simple_dummy_events.c
> index ed63ffd849f8..7ec2a0bb0807 100644
> --- a/drivers/iio/dummy/iio_simple_dummy_events.c
> +++ b/drivers/iio/dummy/iio_simple_dummy_events.c
> @@ -72,6 +72,7 @@ int iio_simple_dummy_write_event_config(struct iio_dev *indio_dev,
> st->event_en = state;
> else
> return -EINVAL;
> + break;
> default:
> return -EINVAL;
> }
prev parent reply other threads:[~2017-10-01 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 13:24 [PATCH] iio: dummy: events: Add missing break Lars-Peter Clausen
2017-10-01 10:17 ` 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=20171001111756.057b80f1@archlinux \
--to=jic23@kernel.org \
--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