From: Jonathan Cameron <jic23@kernel.org>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: [PULL] IIO fixes for 3.18 set 1
Date: Tue, 14 Oct 2014 20:00:22 +0100 [thread overview]
Message-ID: <543D72C6.8090604@kernel.org> (raw)
The following changes since commit 0f33be009b89d2268e94194dc4fd01a7851b6d51:
Linux 3.17-rc6 (2014-09-21 15:43:02 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
tags/iio-fixes-for-3.18a
for you to fetch changes up to 75d7ed3b9e7cb79a3b0e1f417fb674d54b4fc668:
iio: adc: mxs-lradc: Disable the clock on probe failure (2014-10-09 21:02:51
+0100)
----------------------------------------------------------------
First round of IIO fixes for the 3.18 cycle.
* ad5933 - fix a null pointer dereference due to an old change that prevents
different channels being registered for the buffer and used for sysfs
interfaces.
* ad5933 - Drop a bonus _raw from attribute names.
* st-sensors - Makes sure the correct number of elements are copied when
filling a local buffer copy.
* mxs-lradc - Disable clocks in a failure path during probe so they aren't
left running.
----------------------------------------------------------------
Fabio Estevam (1):
iio: adc: mxs-lradc: Disable the clock on probe failure
Lars-Peter Clausen (2):
staging:iio:ad5933: Fix NULL pointer deref when enabling buffer
staging:iio:ad5933: Drop "raw" from channel names
Robin van der Gracht (1):
iio: st_sensors: Fix buffer copy
drivers/iio/common/st_sensors/st_sensors_buffer.c | 2 +-
drivers/staging/iio/adc/mxs-lradc.c | 12 ++++++++----
drivers/staging/iio/impedance-analyzer/ad5933.c | 15 ++++++---------
3 files changed, 15 insertions(+), 14 deletions(-)
next reply other threads:[~2014-10-14 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 19:00 Jonathan Cameron [this message]
2014-10-25 2:10 ` [PULL] IIO fixes for 3.18 set 1 Greg KH
-- strict thread matches above, loose matches on Subject: below --
2014-10-14 17:47 Jonathan Cameron
2014-10-14 19:00 ` 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=543D72C6.8090604@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox