From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] 2nd set of IIO fixes for the 5.7 cycle.
Date: Mon, 11 May 2020 20:11:50 +0100 [thread overview]
Message-ID: <20200511201150.13576144@archlinux> (raw)
The following changes since commit c532cc617e6edc4398a9ec5c8f470833966f9f9f:
Merge tag 'iio-fixes-for-5.7a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus (2020-04-20 14:07:00 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.7b
for you to fetch changes up to 928edefbc18cd8433f7df235c6e09a9306e7d580:
iio: sca3000: Remove an erroneous 'get_device()' (2020-05-10 10:53:36 +0100)
----------------------------------------------------------------
iio-fixes-for-5.7b Second set of fixes for IIO in the 5.7 cycle.
Usual mixed bag of breakage in new code and ancient bugs.
ad2s1210
- Fix missing CS change needed to actually read anything.
atlas-sensor
- Avoid clashing scan index with the timestamp channel.
sca3000
- Fix a randomly placed get_device in an error message print.
st_lsm6dsx
- Fix missing unlock in error path.
stm32-adc
- Fix which device is used to request DMA to ensure it's one
that has actually been registered at point of use.
stm32-dfsdm
- Fix which device is used to request DMA to ensure it's one
that has actually been registered at poitn of use.
ti-ads8344
- Fix channel selection.
vf610 dac
- Fix some missing error handling code.
----------------------------------------------------------------
Christophe JAILLET (2):
iio: dac: vf610: Fix an error handling path in 'vf610_dac_probe()'
iio: sca3000: Remove an erroneous 'get_device()'
Dan Carpenter (1):
iio: imu: st_lsm6dsx: unlock on error in st_lsm6dsx_shub_write_raw()
Dragos Bogdan (1):
staging: iio: ad2s1210: Fix SPI reading
Fabrice Gasnier (2):
iio: adc: stm32-adc: fix device used to request dma
iio: adc: stm32-dfsdm: fix device used to request dma
Gregory CLEMENT (1):
iio: adc: ti-ads8344: Fix channel selection
Matt Ranostay (1):
iio: chemical: atlas-sensor: correct DO-SM channels
drivers/iio/accel/sca3000.c | 2 +-
drivers/iio/adc/stm32-adc.c | 8 ++++----
drivers/iio/adc/stm32-dfsdm-adc.c | 21 +++++++++++----------
drivers/iio/adc/ti-ads8344.c | 8 +++++---
drivers/iio/chemical/atlas-sensor.c | 14 +++++++++++++-
drivers/iio/dac/vf610_dac.c | 1 +
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_shub.c | 7 +++++--
drivers/staging/iio/resolver/ad2s1210.c | 17 ++++++++++++-----
8 files changed, 52 insertions(+), 26 deletions(-)
next reply other threads:[~2020-05-11 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 19:11 Jonathan Cameron [this message]
2020-05-15 14:05 ` [PULL] 2nd set of IIO fixes for the 5.7 cycle 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=20200511201150.13576144@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.