From: Lars-Peter Clausen <lars@metafoo.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: inkern: add iio_write_channel_raw
Date: Thu, 27 Nov 2014 09:07:30 +0100 [thread overview]
Message-ID: <5476DBC2.50309@metafoo.de> (raw)
In-Reply-To: <1417041765-12782-1-git-send-email-dbaryshkov@gmail.com>
On 11/26/2014 11:42 PM, Dmitry Eremin-Solenikov wrote:
> Introduce API for easy in-kernel setting of DAC values.
>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Looks good...
> ---
> drivers/iio/inkern.c | 29 +++++++++++++++++++++++++++++
> include/linux/iio/consumer.h | 11 +++++++++++
> 2 files changed, 40 insertions(+)
>
> diff --git a/drivers/iio/inkern.c b/drivers/iio/inkern.c
> index f084610..5b03e69 100644
> --- a/drivers/iio/inkern.c
> +++ b/drivers/iio/inkern.c
> @@ -608,3 +608,32 @@ err_unlock:
> return ret;
> }
> EXPORT_SYMBOL_GPL(iio_get_channel_type);
> +
> +static int iio_channel_write(struct iio_channel *chan, int val, int val2,
> + enum iio_chan_info_enum info)
> +{
> + int ret;
> +
> + ret = chan->indio_dev->info->write_raw(chan->indio_dev,
> + chan->channel, val, val2, info);
> +
> + return ret;
... but this is something the kbuild bot tester will complain about. There
is no need for the ret variable.
> +}
next prev parent reply other threads:[~2014-11-27 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 22:42 [PATCH] iio: inkern: add iio_write_channel_raw Dmitry Eremin-Solenikov
2014-11-27 8:07 ` Lars-Peter Clausen [this message]
2014-12-10 23:01 ` Hartmut Knaack
2014-12-12 10:17 ` Jonathan Cameron
2014-12-12 13:33 ` Dmitry Eremin-Solenikov
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=5476DBC2.50309@metafoo.de \
--to=lars@metafoo.de \
--cc=dbaryshkov@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.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 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.