From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: Re: [PULL] Second set of IIO fixes for the 5.5 cycle.
Date: Sun, 12 Jan 2020 11:46:53 +0000 [thread overview]
Message-ID: <20200112114653.01370ef8@archlinux> (raw)
In-Reply-To: <20200105110051.445c9a95@archlinux>
Hi Greg,
Just wondering if this one slipped through the net?
If we are cutting it a bit fine for the upcoming merge window
then I'm happy if you want to apply these to your staging/staging-next
tree instead of staging/staging-linus.
Thanks,
Jonathan
On Sun, 5 Jan 2020 11:00:51 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> The following changes since commit c05c403b1d123031f86e65e867be2c2e9ee1e7e3:
>
> staging: wfx: fix wrong error message (2019-12-18 15:51:06 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-5.5b
>
> for you to fetch changes up to 80d92ea5f865175bf4cb2cb252b0d1f439c4bcec:
>
> iio: light: vcnl4000: Fix scale for vcnl4040 (2019-12-30 16:48:13 +0000)
>
> ----------------------------------------------------------------
> 2nd Set of IIO fixes for the 5.5 cycle.
>
> * Core
> - Fix buffer alignment calculation. The previous logic meant that scans
> could under some circumstances not have naturally aligned elements.
> In theory someone might have been working around this in userspace, but
> if so we'd have expected them to query this very odd behaviour.
> It's not hit in that many drivers as requires a mixture of channel
> resolutions broad enough to require different packing. The one obvious
> case of timestamps was fine under existing code as they are always the
> last element if enabled and that was handled correctly.
> * ad7124
> - DT channel configuration wasn't using the reg value so would lead
> to some odd mappings and readout of the wrong channels.
> * pms7003
> - Kconfig didn't specify triggered buffer dependency.
> * st_lsm6dsx
> - For the LSM6DS3 the id match wasn't working.
> * vcnl4000
> - Scale was wrong for the vcnl4040
>
> ----------------------------------------------------------------
> Alexandru Tachici (1):
> iio: adc: ad7124: Fix DT channel configuration
>
> Guido Günther (1):
> iio: light: vcnl4000: Fix scale for vcnl4040
>
> Lars Möllendorf (1):
> iio: buffer: align the size of scan bytes to size of the largest element
>
> Stephan Gerhold (1):
> iio: imu: st_lsm6dsx: Fix selection of ST_LSM6DS3_ID
>
> Tomasz Duszynski (1):
> iio: chemical: pms7003: fix unmet triggered buffer dependency
>
> drivers/iio/adc/ad7124.c | 12 +++++-------
> drivers/iio/chemical/Kconfig | 1 +
> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 3 ++-
> drivers/iio/industrialio-buffer.c | 6 +++++-
> drivers/iio/light/vcnl4000.c | 3 ++-
> 5 files changed, 15 insertions(+), 10 deletions(-)
next prev parent reply other threads:[~2020-01-12 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 11:00 [PULL] Second set of IIO fixes for the 5.5 cycle Jonathan Cameron
2020-01-12 11:46 ` Jonathan Cameron [this message]
2020-01-12 11:52 ` Greg KH
2020-01-12 16:35 ` Jonathan Cameron
2020-01-13 11:06 ` Greg KH
2020-01-14 10:11 ` Jonathan Cameron
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=20200112114653.01370ef8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox