From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] Second set of IIO fixes for the 5.3 cycle.
Date: Mon, 12 Aug 2019 20:21:47 +0100 [thread overview]
Message-ID: <20190812202147.065fb84e@archlinux> (raw)
The following changes since commit 09f6109ff4f8003af3370dfee0f73fcf6d20087a:
Merge tag 'iio-fixes-for-5.3a' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus (2019-07-28 11:07:26 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.3b
for you to fetch changes up to b9ddd5091160793ee9fac10da765cf3f53d2aaf0:
iio: adc: max9611: Fix temperature reading in probe (2019-08-05 17:42:24 +0100)
----------------------------------------------------------------
Second set of IIO fix for the 5.3 cycle.
* adf4371
- Calculation of the value to program to control the output frequency
was incorrect.
* max9611
- Fix temperature reading in probe. A recent fix for a wrong mask
meant this code was looked at afresh. A second bug became obvious
in which the return value was used inplace of the desired register
value. This had no visible effect other than a communication test
not actually testing the communications.
----------------------------------------------------------------
Jacopo Mondi (1):
iio: adc: max9611: Fix temperature reading in probe
Nuno Sá (1):
iio: frequency: adf4371: Fix output frequency setting
drivers/iio/adc/max9611.c | 2 +-
drivers/iio/frequency/adf4371.c | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2019-08-12 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 19:21 Jonathan Cameron [this message]
2019-08-12 20:48 ` [PULL] Second set of IIO fixes for the 5.3 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=20190812202147.065fb84e@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.