From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] 3rd set of IIO fixes for 6.1
Date: Wed, 16 Nov 2022 18:56:10 +0000 [thread overview]
Message-ID: <20221116185610.4efb044b@jic23-huawei> (raw)
The following changes since commit 38e9f21f648ed3f9125fe09378da9b2eb08b12d9:
Merge tag 'iio-fixes-for-6.1b' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into char-misc-linus (2022-11-05 11:29:29 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.1c
for you to fetch changes up to 398e3479874f381cca8726ca5d8a31e1bf35a3cd:
dt-bindings: iio: adc: Remove the property "aspeed,trim-data-valid" (2022-11-14 20:20:19 +0000)
----------------------------------------------------------------
3rd set of IIO fixes for the 6.1 cycle.
Usual mixed bunch of driver fixes.
* sw-triggers
- Fix failure to cleanup up list registration in an error path.
* aspeed,adc
- Drop the trim valid dts property as it doesn't account for unprogrammed
OTP and that can be easily detected without it.
* avago,apds9960:
- Fix register address for gesture gain.
* bosch,bma400
- Fix a memory leak in an error path.
* rohm,rpr0521
- Fix missing dependency on IIO_BUFFER/IIO_TRIGGERED_BUFFER.
* ti,afe4403/4404
- Fix out of band read by moving reads down to where they are used.
----------------------------------------------------------------
Alejandro Concepción Rodríguez (1):
iio: light: apds9960: fix wrong register for gesture gain
Billy Tsai (2):
iio: adc: aspeed: Remove the trim valid dts property.
dt-bindings: iio: adc: Remove the property "aspeed,trim-data-valid"
Chen Zhongjin (1):
iio: core: Fix entry not deleted when iio_register_sw_trigger_type() fails
Dong Chenchen (1):
iio: accel: bma400: Fix memory leak in bma400_get_steps_reg()
Paul Gazzillo (1):
iio: light: rpr0521: add missing Kconfig dependencies
Wei Yongjun (2):
iio: health: afe4403: Fix oob read in afe4403_read_raw
iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw
.../devicetree/bindings/iio/adc/aspeed,ast2600-adc.yaml | 7 -------
drivers/iio/accel/bma400_core.c | 4 +++-
drivers/iio/adc/aspeed_adc.c | 11 +++++------
drivers/iio/health/afe4403.c | 5 +++--
drivers/iio/health/afe4404.c | 12 +++++++-----
drivers/iio/industrialio-sw-trigger.c | 6 +++++-
drivers/iio/light/Kconfig | 2 ++
drivers/iio/light/apds9960.c | 12 ++++++------
8 files changed, 31 insertions(+), 28 deletions(-)
next reply other threads:[~2022-11-16 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 18:56 Jonathan Cameron [this message]
2022-11-22 17:19 ` [PULL] 3rd 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=20221116185610.4efb044b@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