From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: lorenzo@kernel.org, Jonathan.Cameron@huawei.com, Stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iio: imu: st_lsm6dsx: fix ODR check in st_lsm6dsx_write_raw" failed to apply to 5.3-stable tree
Date: Sun, 15 Dec 2019 13:10:53 -0500 [thread overview]
Message-ID: <20191215181053.GJ18043@sasha-vm> (raw)
In-Reply-To: <157640221818196@kroah.com>
On Sun, Dec 15, 2019 at 10:30:18AM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.3-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From fc3f6ad7f5dc6c899fbda0255865737bac88c2e0 Mon Sep 17 00:00:00 2001
>From: Lorenzo Bianconi <lorenzo@kernel.org>
>Date: Sun, 27 Oct 2019 19:02:30 +0100
>Subject: [PATCH] iio: imu: st_lsm6dsx: fix ODR check in st_lsm6dsx_write_raw
>
>Since st_lsm6dsx i2c master controller relies on accel device as trigger
>and slave devices can run at different ODRs we must select an accel_odr >=
>slave_odr. Report real accel ODR in st_lsm6dsx_check_odr() in order to
>properly set sensor frequency in st_lsm6dsx_write_raw and avoid to
>report unsupported frequency
>
>Fixes: 6ffb55e5009ff ("iio: imu: st_lsm6dsx: introduce ST_LSM6DSX_ID_EXT sensor ids")
>Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
>Cc: <Stable@vger.kernel.org>
>Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I took in the following as a dependency and queued for 5.3:
40dd73438977 ("iio: imu: st_lsm6dsx: move odr_table in st_lsm6dsx_sensor_settings")
--
Thanks,
Sasha
prev parent reply other threads:[~2019-12-15 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 9:30 FAILED: patch "[PATCH] iio: imu: st_lsm6dsx: fix ODR check in st_lsm6dsx_write_raw" failed to apply to 5.3-stable tree gregkh
2019-12-15 18:10 ` Sasha Levin [this message]
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=20191215181053.GJ18043@sasha-vm \
--to=sashal@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Stable@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lorenzo@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