From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] 2nd set of IIO fixes for 6.1
Date: Thu, 3 Nov 2022 21:10:16 +0000 [thread overview]
Message-ID: <20221103211016.1ddd0e9b@jic23-huawei> (raw)
The following changes since commit d76308f03ee1574b0deffde45604252a51c77f6d:
Revert "coresight: cti: Fix hang in cti_disable_hw()" (2022-10-24 08:33:45 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.1b
for you to fetch changes up to 7c919b619bcc68158921b1bd968f0e704549bbb6:
tools: iio: iio_generic_buffer: Fix read size (2022-11-01 08:48:13 +0000)
----------------------------------------------------------------
2nd set of IIO fixes for 6.1
Another mixed bag of driver fixes.
* atmel,at91-sama5d2
- Drop a 5 degree offset as not needed for production devices.
- Missing iio_trigger_free() in error path.
* bosch,bma400
- Turn power on before trying to read chip ID.
* bosch,bno055
- Avoid uninitialized variable warning (no actual impact)
* meas,ms5611
- Fix multiple instances of driver sharing single prom array.
- Stop forcing SPI speed to max devices supports
* mps,mp2629
- Wrong structure field used to match channel.
- Missing NULL terminator.
* sysfs-trigger
- Fix memory leak in error path.
* tools
- Fix wrong read size when calling with noevents.
----------------------------------------------------------------
Claudiu Beznea (1):
iio: adc: at91-sama5d2_adc: get rid of 5 degrees Celsius adjustment
Dan Carpenter (1):
iio: imu: bno055: uninitialized variable bug in bno055_trigger_handler()
Jonathan Cameron (1):
iio: accel: bma400: Ensure VDDIO is enable defore reading the chip ID.
Matti Vaittinen (1):
tools: iio: iio_generic_buffer: Fix read size
Mitja Spes (2):
iio: pressure: ms5611: fixed value compensation bug
iio: pressure: ms5611: changed hardcoded SPI speed to value limited
Saravanan Sekar (2):
iio: adc: mp2629: fix wrong comparison of channel
iio: adc: mp2629: fix potential array out of bound access
Yang Yingliang (2):
iio: trigger: sysfs: fix possible memory leak in iio_sysfs_trig_init()
iio: adc: at91_adc: fix possible memory leak in at91_adc_allocate_trigger()
drivers/iio/accel/bma400_core.c | 24 ++++++++---------
drivers/iio/adc/at91-sama5d2_adc.c | 6 ++---
drivers/iio/adc/at91_adc.c | 4 ++-
drivers/iio/adc/mp2629_adc.c | 5 ++--
drivers/iio/imu/bno055/bno055.c | 2 +-
drivers/iio/pressure/ms5611.h | 12 +++------
drivers/iio/pressure/ms5611_core.c | 51 +++++++++++++++++++-----------------
drivers/iio/pressure/ms5611_spi.c | 2 +-
drivers/iio/trigger/iio-trig-sysfs.c | 6 ++++-
tools/iio/iio_generic_buffer.c | 4 +--
10 files changed, 60 insertions(+), 56 deletions(-)
next reply other threads:[~2022-11-03 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 21:10 Jonathan Cameron [this message]
2022-11-05 10:33 ` [PULL] 2nd set of IIO fixes for 6.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=20221103211016.1ddd0e9b@jic23-huawei \
--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