From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: [PULL] IIO fixes for 3.19 set 1
Date: Mon, 05 Jan 2015 20:28:54 +0000 [thread overview]
Message-ID: <54AAF406.6040203@kernel.org> (raw)
The following changes since commit 9e8e228f2bf066c37eeee7c25b810cad3235427a:
iio: accel: bmc150: set low default thresholds (2014-11-16 20:25:00 +0000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-3.19a
for you to fetch changes up to 65de7654d39c70c2b942f801cea01590cf7e3458:
iio: iio: Fix iio_channel_read return if channel havn't info (2015-01-01 12:46:48 +0000)
----------------------------------------------------------------
First round of IIO fixes for the 3.19 cycle.
* ad799x fix ad7991/ad7995/ad7999 setup as they do not have a configuration
register to write to. It is written during the convesion sequence. As
such we don't want to write to it at other times.
* Fix iio_channel_read utility function to return to ensure it is apparent
if the relevant element is not there. This avoids using a wrong value
if some channels have the element and others do not.
----------------------------------------------------------------
Fabien Proriol (1):
iio: iio: Fix iio_channel_read return if channel havn't info
Lars-Peter Clausen (1):
iio: ad799x: Fix ad7991/ad7995/ad7999 config setup
drivers/iio/adc/ad799x.c | 15 +++++++++++++--
drivers/iio/inkern.c | 3 +++
2 files changed, 16 insertions(+), 2 deletions(-)
next reply other threads:[~2015-01-05 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 20:28 Jonathan Cameron [this message]
2015-01-09 1:59 ` [PULL] IIO fixes for 3.19 set 1 Greg KH
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=54AAF406.6040203@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.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 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.