From: Jonathan Cameron <jic23@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org
Subject: [PULL] Second set of IIO fixes for the 4.14 cycle.
Date: Sun, 15 Oct 2017 11:51:18 +0100 [thread overview]
Message-ID: <20171015115118.0090f5c9@archlinux> (raw)
The following changes since commit b2e312061c5e9f533c44487862dc405094bf250a:
Merge tag 'iio-fixes-for-4.14a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus (2017-09-25 10:58:22 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-4.14b
for you to fetch changes up to ca4c302398963c0cae29bc168e44cf91e40ff0d3:
iio: adc: at91-sama5d2_adc: fix probe error on missing trigger property (2017-10-14 19:52:07 +0100)
----------------------------------------------------------------
Second set of IIO fixes for the 4.14 cycle.
* ade7759
- Fix a signed extension bug.
* as3935
- The default noise and watch dog settings were such that the device
was unusuable in most applications. Add device tree parameters to
allow it to be configured to something that will actually work.
* at91-sama5d2 adc
- Fix handling of legacy device trees that don't provide the new
trigger edge property.
* dln2-adc
- Fix a missing Kconfig dependency on IIO_TRIGGERED_BUFFER.
* dummy driver
- Add a missing break so that writing in_voltage0_thresh_rising_en
doesn't always result in an error.
* zpa2326
- Drop a test for an always true condition so that gcc won't spit out
and unused variable warning.
----------------------------------------------------------------
Colin Ian King (1):
staging: iio: ade7759: fix signed extension bug on shift of a u8
Eugen Hristev (1):
iio: adc: at91-sama5d2_adc: fix probe error on missing trigger property
Geert Uytterhoeven (1):
iio: pressure: zpa2326: Remove always-true check which confuses gcc
Lars-Peter Clausen (1):
iio: dummy: events: Add missing break
Matt Ranostay (1):
iio: proximity: as3935: noise detection + threshold changes
Randy Dunlap (1):
iio: adc: dln2-adc: fix build error
.../ABI/testing/sysfs-bus-iio-proximity-as3935 | 8 ++++
.../devicetree/bindings/iio/proximity/as3935.txt | 5 +++
drivers/iio/adc/Kconfig | 2 +
drivers/iio/adc/at91-sama5d2_adc.c | 45 ++++++++++++++--------
drivers/iio/dummy/iio_simple_dummy_events.c | 1 +
drivers/iio/pressure/zpa2326.c | 10 ++---
drivers/iio/proximity/as3935.c | 43 +++++++++++++++++++--
drivers/staging/iio/meter/ade7759.c | 2 +-
8 files changed, 89 insertions(+), 27 deletions(-)
next reply other threads:[~2017-10-15 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 10:51 Jonathan Cameron [this message]
2017-10-15 11:16 ` [PULL] Second set of IIO fixes for the 4.14 cycle 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=20171015115118.0090f5c9@archlinux \
--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.