From: Jonathan Cameron <jic23@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-iio@vger.kernel.org
Subject: [PULL] IIO fixes 3.14 set 2
Date: Sat, 08 Feb 2014 19:41:18 +0000 [thread overview]
Message-ID: <52F6885E.8060304@kernel.org> (raw)
The following changes since commit 6b89db36b3ab7c4b99027873e1de4be8d07387d4:
wlags49_h2: Fix overflow in wireless_set_essid() (2014-02-07 11:10:08 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-3.14b
for you to fetch changes up to 55b40d37311807a6bb2acdae0df904f54a0da3ae:
iio: max1363: Use devm_regulator_get_optional for optional regulator (2014-02-08 11:46:00 +0000)
----------------------------------------------------------------
Second round of IIO fixes for the 3.14 cycle.
Another mixed bag, including some that were not in round 1 because
they applied to elements that went in during the merge window whereas
round 1 predated that. I have been effectively out of action for 3 weeks
so will take a little while to catch up with my backlog.
* mag3110 - report busy in read_raw / write_raw when buffered capture
is underway to avoid either changing the characteristics of the capture or
causing capture issues by reading data destined for the buffer.
* mag3110 - fix a failure to specify leading zeros when formatting a decimal
number.
* lradc - fix a buffer overflow and incorrect reporting of scale for voltage
channel 15
* lradc - drop some scale_available attributes for elements that don't actually
exist. These could otherwise cause some interesting issues for userspace.
* ad799x - a typo in the events information mask resulted in some nasty crashes
on failed probes.
* ak8975 - fix scale attribute output to avoid incorrect intepretation of
readings in userspace.
* adis16400 - make sure the timestamp is the last element in all channel_spec
arrays as this assumption is made by the buffer filling code, but was not
true previously.
* bma180 - correctly use modifiers to distinguish the channels rather than
indexes. This brings the abi inline with the standard option for 3 axis
accelerometers.
* max1363 - use devm_regulator_get_optional instead of the non optional case
to allow the device to successfully probe when a regulator is not specified.
----------------------------------------------------------------
Alexandre Belloni (2):
iio: mxs-lradc: fix buffer overflow
iio: mxs-lradc: remove useless scale_available files
Beomho Seo (1):
iio: ak8975: Fix calculation formula for convert micro tesla to gauss unit
Guenter Roeck (1):
iio: max1363: Use devm_regulator_get_optional for optional regulator
Hartmut Knaack (1):
staging:iio:ad799x fix typo in ad799x_events[]
Marcus Folkesson (1):
iio: adis16400: Set timestamp as the last element in chan_spec
Peter Meerwald (3):
iio:magnetometer:mag3110: Report busy in _read_raw() / write_raw() when buffer is enabled
iio:magnetometer:mag3110: Fix output of decimal digits in show_int_plus_micros()
iio:accel:bma180: Use modifier instead of index in channel specification
drivers/iio/accel/bma180.c | 16 ++++++++--------
drivers/iio/adc/max1363.c | 2 +-
drivers/iio/imu/adis16400.h | 1 +
drivers/iio/imu/adis16400_core.c | 10 +++++-----
drivers/iio/magnetometer/ak8975.c | 16 +++++++++-------
drivers/iio/magnetometer/mag3110.c | 8 +++++++-
drivers/staging/iio/adc/ad799x_core.c | 2 +-
drivers/staging/iio/adc/mxs-lradc.c | 6 +-----
8 files changed, 33 insertions(+), 28 deletions(-)
next reply other threads:[~2014-02-08 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 19:41 Jonathan Cameron [this message]
2014-02-08 21:30 ` [PULL] IIO fixes 3.14 set 2 Greg Kroah-Hartman
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=52F6885E.8060304@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.